plotly.graph_objs Module
Functions
plotly.graph_objs.Bar
plotly.graph_objs.Barpolar
plotly.graph_objs.Box
plotly.graph_objs.Candlestick
plotly.graph_objs.Carpet
plotly.graph_objs.Choropleth
plotly.graph_objs.Choroplethmapbox
plotly.graph_objs.Cone
plotly.graph_objs.Contour
plotly.graph_objs.Contourcarpet
plotly.graph_objs.Densitymapbox
plotly.graph_objs.Figure
plotly.graph_objs.Funnel
plotly.graph_objs.Funnelarea
plotly.graph_objs.Heatmap
plotly.graph_objs.Heatmapgl
plotly.graph_objs.Histogram
plotly.graph_objs.Histogram2d
plotly.graph_objs.Histogram2dContour
plotly.graph_objs.Icicle
plotly.graph_objs.Image
plotly.graph_objs.Indicator
plotly.graph_objs.Isosurface
plotly.graph_objs.Layout
plotly.graph_objs.Mesh3d
plotly.graph_objs.Ohlc
plotly.graph_objs.Parcats
plotly.graph_objs.Parcoords
plotly.graph_objs.Pie
plotly.graph_objs.Pointcloud
plotly.graph_objs.Sankey
plotly.graph_objs.Scatter
plotly.graph_objs.Scatter3d
plotly.graph_objs.Scattercarpet
plotly.graph_objs.Scattergeo
plotly.graph_objs.Scattergl
plotly.graph_objs.Scattermapbox
plotly.graph_objs.Scatterpolar
plotly.graph_objs.Scatterpolargl
plotly.graph_objs.Scattersmith
plotly.graph_objs.Scatterternary
plotly.graph_objs.Splom
plotly.graph_objs.Streamtube
plotly.graph_objs.Sunburst
plotly.graph_objs.Surface
plotly.graph_objs.Table
plotly.graph_objs.Treemap
plotly.graph_objs.Violin
plotly.graph_objs.Volume
plotly.graph_objs.Waterfall
Functions
plotly.graph_objs.Bar([_deprecated=], [alignmentgroup=], [base=], [basesrc=], [cliponaxis=], [constraintext=], [customdata=], [customdatasrc=], [dx=], [dy=], [error_x=], [error_y=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextanchor=], [insidetextfont=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [offset=], [offsetgroup=], [offsetsrc=], [opacity=], [orientation=], [outsidetextfont=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textangle=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [width=], [widthsrc=], [x=], [x0=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [ycalendar=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Bar
Create a new ‘Bar’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.base- Sets where the bar base is drawn (in position axis units). In *stack* or *relative* barmode, traces that set *base* will be excluded and drawn in *overlay* mode instead.basesrc- Sets the source reference on Chart Studio Cloud for `base`.cliponaxis- Determines whether the text nodes are clipped about the subplot axes. To show the text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.constraintext- Constrain the size of text inside or outside a bar to be no larger than the bar itself.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `value` and `label`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextanchor- Determines if texts are kept at center or start/end points in `textposition` *inside* mode.insidetextfont- Sets the font used for `text` lying inside the bar.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.offset- Shifts the position where the bar is drawn (in position axis units). In *group* barmode, traces that set *offset* will be excluded and drawn in *overlay* mode instead.offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.offsetsrc- Sets the source reference on Chart Studio Cloud for `offset`.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the bars. With *v* (*h*), the value of the each bar spans along the vertical (horizontal).outsidetextfont- Sets the font used for `text` lying outside the bar.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textangle- Sets the angle of the tick labels with respect to the bar. For example, a `tickangle` of -90 draws the tick labels vertically. With *auto* the texts may automatically be rotated to fit with the maximum size in bars.textfont- Sets the font used for `text`.textposition- Specifies the location of the `text`. *inside* positions `text` inside, next to the bar end (rotated and scaled if needed). *outside* positions `text` outside, next to the bar end (scaled if needed), unless there is another bar stacked on this one, then the text gets pushed inside. *auto* tries to position `text` inside the bar, but if the bar is too small and no bar is stacked on this one the text is moved outside. If *none*, no text appears.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `value` and `label`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).width- Sets the bar width (in position axis units).widthsrc- Sets the source reference on Chart Studio Cloud for `width`.x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Barpolar([base=], [basesrc=], [customdata=], [customdatasrc=], [dr=], [dtheta=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [offset=], [offsetsrc=], [opacity=], [r=], [r0=], [rsrc=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [text=], [textsrc=], [theta=], [theta0=], [thetasrc=], [thetaunit=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [width=], [widthsrc=]) → Barpolar
Create a new ‘Barpolar’ object
base- Sets where the bar base is drawn (in radial axis units). In *stack* barmode, traces that set *base* will be excluded and drawn in *overlay* mode instead.basesrc- Sets the source reference on Chart Studio Cloud for `base`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dr- Sets the r coordinate step.dtheta- Sets the theta coordinate step. By default, the `dtheta` step equals the subplot's period divided by the length of the `r` coordinates.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.offset- Shifts the angular position where the bar is drawn (in *thetatunit* units).offsetsrc- Sets the source reference on Chart Studio Cloud for `offset`.opacity- Sets the opacity of the trace.r- Sets the radial coordinatesr0- Alternate to `r`. Builds a linear space of r coordinates. Use with `dr` where `r0` is the starting coordinate and `dr` the step.rsrc- Sets the source reference on Chart Studio Cloud for `r`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a polar subplot. If *polar* (the default value), the data refer to `layout.polar`. If *polar2*, the data refer to `layout.polar2`, and so on.text- Sets hover text elements associated with each bar. If a single string, the same string appears over all bars. If an array of string, the items are mapped in order to the this trace's coordinates.textsrc- Sets the source reference on Chart Studio Cloud for `text`.theta- Sets the angular coordinatestheta0- Alternate to `theta`. Builds a linear space of theta coordinates. Use with `dtheta` where `theta0` is the starting coordinate and `dtheta` the step.thetasrc- Sets the source reference on Chart Studio Cloud for `theta`.thetaunit- Sets the unit of input *theta* values. Has an effect only when on *linear* angular axes.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).width- Sets the bar angular width (in *thetaunit* units).widthsrc- Sets the source reference on Chart Studio Cloud for `width`.
plotly.graph_objs.Box([alignmentgroup=], [boxmean=], [boxpoints=], [customdata=], [customdatasrc=], [dx=], [dy=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [jitter=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [lowerfence=], [lowerfencesrc=], [marker=], [mean=], [meansrc=], [median=], [mediansrc=], [meta=], [metasrc=], [name=], [notched=], [notchspan=], [notchspansrc=], [notchwidth=], [offsetgroup=], [opacity=], [orientation=], [pointpos=], [q1=], [q1src=], [q3=], [q3src=], [quartilemethod=], [sd=], [sdsrc=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [unselected=], [upperfence=], [upperfencesrc=], [visible=], [whiskerwidth=], [width=], [x=], [x0=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [ycalendar=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Box
Create a new ‘Box’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.boxmean- If *true*, the mean of the box(es)' underlying distribution is drawn as a dashed line inside the box(es). If *sd* the standard deviation is also drawn. Defaults to *true* when `mean` is set. Defaults to *sd* when `sd` is set Otherwise defaults to *false*.boxpoints- If *outliers*, only the sample points lying outside the whiskers are shown If *suspectedoutliers*, the outlier points are shown and points either less than 4*Q1-3*Q3 or greater than 4*Q3-3*Q1 are highlighted (see `outliercolor`) If *all*, all sample points are shown If *false*, only the box(es) are shown with no sample points Defaults to *suspectedoutliers* when `marker.outliercolor` or `marker.line.outliercolor` is set. Defaults to *all* under the q1/median/q3 signature. Otherwise defaults to *outliers*.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step for multi-box traces set using q1/median/q3.dy- Sets the y coordinate step for multi-box traces set using q1/median/q3.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual boxes or sample points or both?hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.jitter- Sets the amount of jitter in the sample points drawn. If *0*, the sample points align along the distribution axis. If *1*, the sample points are drawn in a random jitter of width equal to the width of the box(es).legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.lowerfence- Sets the lower fence values. There should be as many items as the number of boxes desired. This attribute has effect only under the q1/median/q3 signature. If `lowerfence` is not provided but a sample (in `y` or `x`) is set, we compute the lower as the last sample point below 1.5 times the IQR.lowerfencesrc- Sets the source reference on Chart Studio Cloud for `lowerfence`.mean- Sets the mean values. There should be as many items as the number of boxes desired. This attribute has effect only under the q1/median/q3 signature. If `mean` is not provided but a sample (in `y` or `x`) is set, we compute the mean for each box using the sample values.meansrc- Sets the source reference on Chart Studio Cloud for `mean`.median- Sets the median values. There should be as many items as the number of boxes desired.mediansrc- Sets the source reference on Chart Studio Cloud for `median`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover. For box traces, the name will also be used for the position coordinate, if `x` and `x0` (`y` and `y0` if horizontal) are missing and the position axis is categoricalnotched- Determines whether or not notches are drawn. Notches displays a confidence interval around the median. We compute the confidence interval as median +/- 1.57 * IQR / sqrt(N), where IQR is the interquartile range and N is the sample size. If two boxes' notches do not overlap there is 95% confidence their medians differ. See https://sites.google.com/site/davidsstatistics/home/notched-box-plots for more info. Defaults to *false* unless `notchwidth` or `notchspan` is set.notchspan- Sets the notch span from the boxes' `median` values. There should be as many items as the number of boxes desired. This attribute has effect only under the q1/median/q3 signature. If `notchspan` is not provided but a sample (in `y` or `x`) is set, we compute it as 1.57 * IQR / sqrt(N), where N is the sample size.notchspansrc- Sets the source reference on Chart Studio Cloud for `notchspan`.notchwidth- Sets the width of the notches relative to the box' width. For example, with 0, the notches are as wide as the box(es).offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the box(es). If *v* (*h*), the distribution is visualized along the vertical (horizontal).pointpos- Sets the position of the sample points in relation to the box(es). If *0*, the sample points are places over the center of the box(es). Positive (negative) values correspond to positions to the right (left) for vertical boxes and above (below) for horizontal boxesq1- Sets the Quartile 1 values. There should be as many items as the number of boxes desired.q1src- Sets the source reference on Chart Studio Cloud for `q1`.q3- Sets the Quartile 3 values. There should be as many items as the number of boxes desired.q3src- Sets the source reference on Chart Studio Cloud for `q3`.quartilemethod- Sets the method used to compute the sample's Q1 and Q3 quartiles. The *linear* method uses the 25th percentile for Q1 and 75th percentile for Q3 as computed using method #10 (listed on http://jse.amstat.org/v14n3/langford.html). The *exclusive* method uses the median to divide the ordered dataset into two halves if the sample is odd, it does not include the median in either half - Q1 is then the median of the lower half and Q3 the median of the upper half. The *inclusive* method also uses the median to divide the ordered dataset into two halves but if the sample is odd, it includes the median in both halves - Q1 is then the median of the lower half and Q3 the median of the upper half.sd- Sets the standard deviation values. There should be as many items as the number of boxes desired. This attribute has effect only under the q1/median/q3 signature. If `sd` is not provided but a sample (in `y` or `x`) is set, we compute the standard deviation for each box using the sample values.sdsrc- Sets the source reference on Chart Studio Cloud for `sd`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets the text elements associated with each sample value. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.upperfence- Sets the upper fence values. There should be as many items as the number of boxes desired. This attribute has effect only under the q1/median/q3 signature. If `upperfence` is not provided but a sample (in `y` or `x`) is set, we compute the lower as the last sample point above 1.5 times the IQR.upperfencesrc- Sets the source reference on Chart Studio Cloud for `upperfence`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).whiskerwidth- Sets the width of the whiskers relative to the box' width. For example, with 1, the whiskers are as wide as the box(es).width- Sets the width of the box in data coordinate If *0* (default value) the width is automatically selected based on the positions of other box traces in the same subplot.x- Sets the x sample data or coordinates. See overview for more info.x0- Sets the x coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y sample data or coordinates. See overview for more info.y0- Sets the y coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Candlestick([close=], [closesrc=], [customdata=], [customdatasrc=], [decreasing=], [high=], [highsrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [increasing=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [low=], [lowsrc=], [meta=], [metasrc=], [name=], [opacity=], [open=], [opensrc=], [selectedpoints=], [showlegend=], [stream=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [visible=], [whiskerwidth=], [x=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [yaxis=], [yhoverformat=]) → Candlestick
Create a new ‘Candlestick’ object
close- Sets the close values.closesrc- Sets the source reference on Chart Studio Cloud for `close`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.high- Sets the high values.highsrc- Sets the source reference on Chart Studio Cloud for `high`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.low- Sets the low values.lowsrc- Sets the source reference on Chart Studio Cloud for `low`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.open- Sets the open values.opensrc- Sets the source reference on Chart Studio Cloud for `open`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets hover text elements associated with each sample point. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to this trace's sample points.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).whiskerwidth- Sets the width of the whiskers relative to the box' width. For example, with 1, the whiskers are as wide as the box(es).x- Sets the x coordinates. If absent, linear coordinate will be generated.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.
plotly.graph_objs.Carpet([a=], [a0=], [aaxis=], [asrc=], [b=], [b0=], [baxis=], [bsrc=], [carpet=], [cheaterslope=], [color=], [customdata=], [customdatasrc=], [da=], [db=], [font=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [name=], [opacity=], [stream=], [uid=], [uirevision=], [visible=], [x=], [xaxis=], [xsrc=], [y=], [yaxis=], [ysrc=]) → Carpet
Create a new ‘Carpet’ object
a- An array containing values of the first parameter valuea0- Alternate to `a`. Builds a linear space of a coordinates. Use with `da` where `a0` is the starting coordinate and `da` the step.asrc- Sets the source reference on Chart Studio Cloud for `a`.b- A two dimensional array of y coordinates at each carpet point.b0- Alternate to `b`. Builds a linear space of a coordinates. Use with `db` where `b0` is the starting coordinate and `db` the step.bsrc- Sets the source reference on Chart Studio Cloud for `b`.carpet- An identifier for this carpet, so that `scattercarpet` and `contourcarpet` traces can specify a carpet plot on which they liecheaterslope- The shift applied to each successive row of data in creating a cheater plot. Only used if `x` is been omitted.color- Sets default for all colors associated with this axis all at once: line, font, tick, and grid colors. Grid color is lightened by blending this with the plot background Individual pieces can override this.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.da- Sets the a coordinate step. See `a0` for more info.db- Sets the b coordinate step. See `b0` for more info.font- The default font used for axis & tick labels on this carpetids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- A two dimensional array of x coordinates at each carpet point. If omitted, the plot is a cheater plot and the xaxis is hidden by default.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- A two dimensional array of y coordinates at each carpet point.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Choropleth([autocolorscale=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [featureidkey=], [geo=], [geojson=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [locationmode=], [locations=], [locationssrc=], [marker=], [meta=], [metasrc=], [name=], [reversescale=], [selected=], [selectedpoints=], [showlegend=], [showscale=], [stream=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [z=], [zauto=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Choropleth
Create a new ‘Choropleth’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.featureidkey- Sets the key in GeoJSON features which is used as id to match the items included in the `locations` array. Only has an effect when `geojson` is set. Support nested property, for example *properties.name*.geo- Sets a reference between this trace's geospatial coordinates and a geographic map. If *geo* (the default value), the geospatial coordinates refer to `layout.geo`. If *geo2*, the geospatial coordinates refer to `layout.geo2`, and so on.geojson- Sets optional GeoJSON data associated with this trace. If not given, the features on the base map are used. It can be set as a valid GeoJSON object or as a URL string. Note that we only accept GeoJSONs of type *FeatureCollection* or *Feature* with geometries of type *Polygon* or *MultiPolygon*.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.locationmode- Determines the set of locations used to match entries in `locations` to regions on the map. Values *ISO-3*, *USA-states*, *country names* correspond to features on the base map and value *geojson-id* corresponds to features from a custom GeoJSON linked to the `geojson` attribute.locations- Sets the coordinates via location IDs or names. See `locationmode` for more info.locationssrc- Sets the source reference on Chart Studio Cloud for `locations`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with each location.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).z- Sets the color values.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Choroplethmapbox([autocolorscale=], [below=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [featureidkey=], [geojson=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [locations=], [locationssrc=], [marker=], [meta=], [metasrc=], [name=], [reversescale=], [selected=], [selectedpoints=], [showlegend=], [showscale=], [stream=], [subplot=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [z=], [zauto=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Choroplethmapbox
Create a new ‘Choroplethmapbox’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.below- Determines if the choropleth polygons will be inserted before the layer with the specified ID. By default, choroplethmapbox traces are placed above the water layers. If set to '', the layer will be inserted above every existing layer.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.featureidkey- Sets the key in GeoJSON features which is used as id to match the items included in the `locations` array. Support nested property, for example *properties.name*.geojson- Sets the GeoJSON data associated with this trace. It can be set as a valid GeoJSON object or as a URL string. Note that we only accept GeoJSONs of type *FeatureCollection* or *Feature* with geometries of type *Polygon* or *MultiPolygon*.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `properties` Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.locations- Sets which features found in *geojson* to plot using their feature `id` field.locationssrc- Sets the source reference on Chart Studio Cloud for `locations`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.subplot- Sets a reference between this trace's data coordinates and a mapbox subplot. If *mapbox* (the default value), the data refer to `layout.mapbox`. If *mapbox2*, the data refer to `layout.mapbox2`, and so on.text- Sets the text elements associated with each location.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).z- Sets the color values.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Cone([anchor=], [autocolorscale=], [cauto=], [cmax=], [cmid=], [cmin=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [scene=], [showlegend=], [showscale=], [sizemode=], [sizeref=], [stream=], [text=], [textsrc=], [u=], [uhoverformat=], [uid=], [uirevision=], [usrc=], [v=], [vhoverformat=], [visible=], [vsrc=], [w=], [whoverformat=], [wsrc=], [x=], [xhoverformat=], [xsrc=], [y=], [yhoverformat=], [ysrc=], [z=], [zhoverformat=], [zsrc=]) → Cone
Create a new ‘Cone’ object
anchor- Sets the cones' anchor with respect to their x/y/z positions. Note that *cm* denote the cone's center of mass which corresponds to 1/4 from the tail to tip.autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here u/v/w norm) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as u/v/w norm and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as u/v/w norm. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as u/v/w norm and if set, `cmax` must be set as well.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `norm` Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.sizemode- Determines whether `sizeref` is set as a *scaled* (i.e unitless) scalar (normalized by the max u/v/w norm in the vector field) or as *absolute* value (in the same units as the vector field).sizeref- Adjusts the cone size scaling. The size of the cones is determined by their u/v/w norm multiplied a factor and `sizeref`. This factor (computed internally) corresponds to the minimum "time" to travel across two successive x/y/z positions at the average velocity of those two successive positions. All cones in a given trace use the same factor. With `sizemode` set to *scaled*, `sizeref` is unitless, its default value is *0.5* With `sizemode` set to *absolute*, `sizeref` has the same units as the u/v/w vector field, its the default value is half the sample's maximum vector norm.text- Sets the text elements associated with the cones. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.u- Sets the x components of the vector field.uhoverformat- Sets the hover text formatting rulefor `u` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.usrc- Sets the source reference on Chart Studio Cloud for `u`.v- Sets the y components of the vector field.vhoverformat- Sets the hover text formatting rulefor `v` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).vsrc- Sets the source reference on Chart Studio Cloud for `v`.w- Sets the z components of the vector field.whoverformat- Sets the hover text formatting rulefor `w` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.wsrc- Sets the source reference on Chart Studio Cloud for `w`.x- Sets the x coordinates of the vector field and of the displayed cones.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates of the vector field and of the displayed cones.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the z coordinates of the vector field and of the displayed cones.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Contour([autocolorscale=], [autocontour=], [coloraxis=], [colorbar=], [colorscale=], [connectgaps=], [contours=], [customdata=], [customdatasrc=], [dx=], [dy=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoverongaps=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [meta=], [metasrc=], [name=], [ncontours=], [opacity=], [reversescale=], [showlegend=], [showscale=], [stream=], [text=], [textfont=], [textsrc=], [texttemplate=], [transform=], [transpose=], [uid=], [uirevision=], [visible=], [x=], [x0=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [xtype=], [y=], [y0=], [yaxis=], [ycalendar=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=], [ytype=], [z=], [zauto=], [zhoverformat=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Contour
Create a new ‘Contour’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.autocontour- Determines whether or not the contour level attributes are picked by an algorithm. If *true*, the number of contour levels can be set in `ncontours`. If *false*, set the contour level attributes in `contours`.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the `z` data are filled in. It is defaulted to true if `z` is a one dimensional array otherwise it is defaulted to false.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.fillcolor- Sets the fill color if `contours.type` is *constraint*. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoverongaps- Determines whether or not gaps (i.e. {nan} or missing values) in the `z` data have hover labels associated with them.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.ncontours- Sets the maximum number of contour levels. The actual number of contours will be chosen automatically to be less than or equal to the value of `ncontours`. Has an effect only if `autocontour` is *true* or if `contours.size` is missing.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with each z value.textfont- For this trace it only has an effect if `coloring` is set to *heatmap*. Sets the text font.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- For this trace it only has an effect if `coloring` is set to *heatmap*. Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `x`, `y`, `z` and `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.transpose- Transposes the z data.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.xtype- If *array*, the heatmap's x coordinates are given by *x* (the default behavior when `x` is provided). If *scaled*, the heatmap's x coordinates are given by *x0* and *dx* (the default behavior when `x` is not provided).y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.ytype- If *array*, the heatmap's y coordinates are given by *y* (the default behavior when `y` is provided) If *scaled*, the heatmap's y coordinates are given by *y0* and *dy* (the default behavior when `y` is not provided)z- Sets the z data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Contourcarpet([a=], [a0=], [asrc=], [atype=], [autocolorscale=], [autocontour=], [b=], [b0=], [bsrc=], [btype=], [carpet=], [coloraxis=], [colorbar=], [colorscale=], [contours=], [customdata=], [customdatasrc=], [da=], [db=], [fillcolor=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [meta=], [metasrc=], [name=], [ncontours=], [opacity=], [reversescale=], [showlegend=], [showscale=], [stream=], [text=], [textsrc=], [transpose=], [uid=], [uirevision=], [visible=], [xaxis=], [yaxis=], [z=], [zauto=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Contourcarpet
Create a new ‘Contourcarpet’ object
a- Sets the x coordinates.a0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.asrc- Sets the source reference on Chart Studio Cloud for `a`.atype- If *array*, the heatmap's x coordinates are given by *x* (the default behavior when `x` is provided). If *scaled*, the heatmap's x coordinates are given by *x0* and *dx* (the default behavior when `x` is not provided).autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.autocontour- Determines whether or not the contour level attributes are picked by an algorithm. If *true*, the number of contour levels can be set in `ncontours`. If *false*, set the contour level attributes in `contours`.b- Sets the y coordinates.b0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.bsrc- Sets the source reference on Chart Studio Cloud for `b`.btype- If *array*, the heatmap's y coordinates are given by *y* (the default behavior when `y` is provided) If *scaled*, the heatmap's y coordinates are given by *y0* and *dy* (the default behavior when `y` is not provided)carpet- The `carpet` of the carpet axes on which this contour trace liescoloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.da- Sets the x coordinate step. See `x0` for more info.db- Sets the y coordinate step. See `y0` for more info.fillcolor- Sets the fill color if `contours.type` is *constraint*. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.ncontours- Sets the maximum number of contour levels. The actual number of contours will be chosen automatically to be less than or equal to the value of `ncontours`. Has an effect only if `autocontour` is *true* or if `contours.size` is missing.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with each z value.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transpose- Transposes the z data.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.z- Sets the z data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Densitymapbox([autocolorscale=], [below=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [lat=], [latsrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lon=], [lonsrc=], [meta=], [metasrc=], [name=], [opacity=], [radius=], [radiussrc=], [reversescale=], [showlegend=], [showscale=], [stream=], [subplot=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [visible=], [z=], [zauto=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Densitymapbox
Create a new ‘Densitymapbox’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.below- Determines if the densitymapbox trace will be inserted before the layer with the specified ID. By default, densitymapbox traces are placed below the first layer of type symbol If set to '', the layer will be inserted above every existing layer.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (lon,lat) pair If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.lat- Sets the latitude coordinates (in degrees North).latsrc- Sets the source reference on Chart Studio Cloud for `lat`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.lon- Sets the longitude coordinates (in degrees East).lonsrc- Sets the source reference on Chart Studio Cloud for `lon`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.radius- Sets the radius of influence of one `lon` / `lat` point in pixels. Increasing the value makes the densitymapbox trace smoother, but less detailed.radiussrc- Sets the source reference on Chart Studio Cloud for `radius`.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.subplot- Sets a reference between this trace's data coordinates and a mapbox subplot. If *mapbox* (the default value), the data refer to `layout.mapbox`. If *mapbox2*, the data refer to `layout.mapbox2`, and so on.text- Sets text elements associated with each (lon,lat) pair If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).z- Sets the points' weight. For example, a value of 10 would be equivalent to having 10 points of weight 1 in the same spotzauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Figure() → Figure
Create a new ‘Figure’ object
plotly.graph_objs.Funnel([alignmentgroup=], [cliponaxis=], [connector=], [constraintext=], [customdata=], [customdatasrc=], [dx=], [dy=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextanchor=], [insidetextfont=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [offset=], [offsetgroup=], [opacity=], [orientation=], [outsidetextfont=], [selectedpoints=], [showlegend=], [stream=], [text=], [textangle=], [textfont=], [textinfo=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [visible=], [width=], [x=], [x0=], [xaxis=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Funnel
Create a new ‘Funnel’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.cliponaxis- Determines whether the text nodes are clipped about the subplot axes. To show the text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.constraintext- Constrain the size of text inside or outside a bar to be no larger than the bar itself.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `percentInitial`, `percentPrevious` and `percentTotal`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextanchor- Determines if texts are kept at center or start/end points in `textposition` *inside* mode.insidetextfont- Sets the font used for `text` lying inside the bar.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.offset- Shifts the position where the bar is drawn (in position axis units). In *group* barmode, traces that set *offset* will be excluded and drawn in *overlay* mode instead.offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the funnels. With *v* (*h*), the value of the each bar spans along the vertical (horizontal). By default funnels are tend to be oriented horizontally; unless only *y* array is presented or orientation is set to *v*. Also regarding graphs including only 'horizontal' funnels, *autorange* on the *y-axis* are set to *reversed*.outsidetextfont- Sets the font used for `text` lying outside the bar.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textangle- Sets the angle of the tick labels with respect to the bar. For example, a `tickangle` of -90 draws the tick labels vertically. With *auto* the texts may automatically be rotated to fit with the maximum size in bars.textfont- Sets the font used for `text`.textinfo- Determines which trace information appear on the graph. In the case of having multiple funnels, percentages & totals are computed separately (per trace).textposition- Specifies the location of the `text`. *inside* positions `text` inside, next to the bar end (rotated and scaled if needed). *outside* positions `text` outside, next to the bar end (scaled if needed), unless there is another bar stacked on this one, then the text gets pushed inside. *auto* tries to position `text` inside the bar, but if the bar is too small and no bar is stacked on this one the text is moved outside. If *none*, no text appears.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `percentInitial`, `percentPrevious`, `percentTotal`, `label` and `value`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).width- Sets the bar width (in position axis units).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Funnelarea([aspectratio=], [baseratio=], [customdata=], [customdatasrc=], [dlabel=], [domain=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextfont=], [label0=], [labels=], [labelssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [opacity=], [scalegroup=], [showlegend=], [stream=], [text=], [textfont=], [textinfo=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [title=], [transform=], [uid=], [uirevision=], [values=], [valuessrc=], [visible=]) → Funnelarea
Create a new ‘Funnelarea’ object
aspectratio- Sets the ratio between height and widthbaseratio- Sets the ratio between bottom length and maximum top length.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dlabel- Sets the label step. See `label0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `label`, `color`, `value`, `text` and `percent`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextfont- Sets the font used for `textinfo` lying inside the sector.label0- Alternate to `labels`. Builds a numeric set of labels. Use with `dlabel` where `label0` is the starting label and `dlabel` the step.labels- Sets the sector labels. If `labels` entries are duplicated, we sum associated `values` or simply count occurrences if `values` is not provided. For other array attributes (including color) we use the first non-empty entry among all occurrences of the label.labelssrc- Sets the source reference on Chart Studio Cloud for `labels`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.scalegroup- If there are multiple funnelareas that should be sized according to their totals, link them by providing a non-empty group id here shared by every trace in the same group.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each sector. If trace `textinfo` contains a *text* flag, these elements will be seen on the chart. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the font used for `textinfo`.textinfo- Determines which trace information appear on the graph.textposition- Specifies the location of the `textinfo`.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `label`, `color`, `value`, `text` and `percent`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.values- Sets the values of the sectors. If omitted, we count occurrences of each label.valuessrc- Sets the source reference on Chart Studio Cloud for `values`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Heatmap([autocolorscale=], [coloraxis=], [colorbar=], [colorscale=], [connectgaps=], [customdata=], [customdatasrc=], [dx=], [dy=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoverongaps=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [showlegend=], [showscale=], [stream=], [text=], [textfont=], [textsrc=], [texttemplate=], [transform=], [transpose=], [uid=], [uirevision=], [visible=], [x=], [x0=], [xaxis=], [xcalendar=], [xgap=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [xtype=], [y=], [y0=], [yaxis=], [ycalendar=], [ygap=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=], [ytype=], [z=], [zauto=], [zhoverformat=], [zmax=], [zmid=], [zmin=], [zsmooth=], [zsrc=]) → Heatmap
Create a new ‘Heatmap’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the `z` data are filled in. It is defaulted to true if `z` is a one dimensional array and `zsmooth` is not false; otherwise it is defaulted to false.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoverongaps- Determines whether or not gaps (i.e. {nan} or missing values) in the `z` data have hover labels associated with them.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with each z value.textfont- Sets the text font.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `x`, `y`, `z` and `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.transpose- Transposes the z data.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xgap- Sets the horizontal gap (in pixels) between bricks.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.xtype- If *array*, the heatmap's x coordinates are given by *x* (the default behavior when `x` is provided). If *scaled*, the heatmap's x coordinates are given by *x0* and *dx* (the default behavior when `x` is not provided).y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.ygap- Sets the vertical gap (in pixels) between bricks.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.ytype- If *array*, the heatmap's y coordinates are given by *y* (the default behavior when `y` is provided) If *scaled*, the heatmap's y coordinates are given by *y0* and *dy* (the default behavior when `y` is not provided)z- Sets the z data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsmooth- Picks a smoothing algorithm use to smooth `z` data.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Heatmapgl([autocolorscale=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [dx=], [dy=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [showscale=], [stream=], [text=], [textsrc=], [transform=], [transpose=], [uid=], [uirevision=], [visible=], [x=], [x0=], [xaxis=], [xsrc=], [xtype=], [y=], [y0=], [yaxis=], [ysrc=], [ytype=], [z=], [zauto=], [zmax=], [zmid=], [zmin=], [zsmooth=], [zsrc=]) → Heatmapgl
Create a new ‘Heatmapgl’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with each z value.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.transpose- Transposes the z data.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xsrc- Sets the source reference on Chart Studio Cloud for `x`.xtype- If *array*, the heatmap's x coordinates are given by *x* (the default behavior when `x` is provided). If *scaled*, the heatmap's x coordinates are given by *x0* and *dx* (the default behavior when `x` is not provided).y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ysrc- Sets the source reference on Chart Studio Cloud for `y`.ytype- If *array*, the heatmap's y coordinates are given by *y* (the default behavior when `y` is provided) If *scaled*, the heatmap's y coordinates are given by *y0* and *dy* (the default behavior when `y` is not provided)z- Sets the z data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsmooth- Picks a smoothing algorithm use to smooth `z` data.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Histogram([_deprecated=], [alignmentgroup=], [autobinx=], [autobiny=], [bingroup=], [cliponaxis=], [constraintext=], [cumulative=], [customdata=], [customdatasrc=], [error_x=], [error_y=], [histfunc=], [histnorm=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextanchor=], [insidetextfont=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [nbinsx=], [nbinsy=], [offsetgroup=], [opacity=], [orientation=], [outsidetextfont=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textangle=], [textfont=], [textposition=], [textsrc=], [texttemplate=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [x=], [xaxis=], [xbins=], [xcalendar=], [xhoverformat=], [xsrc=], [y=], [yaxis=], [ybins=], [ycalendar=], [yhoverformat=], [ysrc=]) → Histogram
Create a new ‘Histogram’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.autobinx- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobinx` is not needed. However, we accept `autobinx: true` or `false` and will update `xbins` accordingly before deleting `autobinx` from the trace.autobiny- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobiny` is not needed. However, we accept `autobiny: true` or `false` and will update `ybins` accordingly before deleting `autobiny` from the trace.bingroup- Set a group of histogram traces which will have compatible bin settings. Note that traces on the same subplot and with the same *orientation* under `barmode` *stack*, *relative* and *group* are forced into the same bingroup, Using `bingroup`, traces under `barmode` *overlay* and on different axes (of the same axis type) can have compatible bin settings. Note that histogram and histogram2d* trace can share the same `bingroup`cliponaxis- Determines whether the text nodes are clipped about the subplot axes. To show the text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.constraintext- Constrain the size of text inside or outside a bar to be no larger than the bar itself.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.histfunc- Specifies the binning function used for this histogram trace. If *count*, the histogram values are computed by counting the number of values lying inside each bin. If *sum*, *avg*, *min*, *max*, the histogram values are computed using the sum, the average, the minimum or the maximum of the values lying inside each bin respectively.histnorm- Specifies the type of normalization used for this histogram trace. If **, the span of each bar corresponds to the number of occurrences (i.e. the number of data points lying inside the bins). If *percent* / *probability*, the span of each bar corresponds to the percentage / fraction of occurrences with respect to the total number of sample points (here, the sum of all bin HEIGHTS equals 100% / 1). If *density*, the span of each bar corresponds to the number of occurrences in a bin divided by the size of the bin interval (here, the sum of all bin AREAS equals the total number of sample points). If *probability density*, the area of each bar corresponds to the probability that an event will fall into the corresponding bin (here, the sum of all bin AREAS equals 1).hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `binNumber` Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextanchor- Determines if texts are kept at center or start/end points in `textposition` *inside* mode.insidetextfont- Sets the font used for `text` lying inside the bar.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.nbinsx- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `xbins.size` is provided.nbinsy- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `ybins.size` is provided.offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the bars. With *v* (*h*), the value of the each bar spans along the vertical (horizontal).outsidetextfont- Sets the font used for `text` lying outside the bar.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets hover text elements associated with each bar. If a single string, the same string appears over all bars. If an array of string, the items are mapped in order to the this trace's coordinates.textangle- Sets the angle of the tick labels with respect to the bar. For example, a `tickangle` of -90 draws the tick labels vertically. With *auto* the texts may automatically be rotated to fit with the maximum size in bars.textfont- Sets the text font.textposition- Specifies the location of the `text`. *inside* positions `text` inside, next to the bar end (rotated and scaled if needed). *outside* positions `text` outside, next to the bar end (scaled if needed), unless there is another bar stacked on this one, then the text gets pushed inside. *auto* tries to position `text` inside the bar, but if the bar is too small and no bar is stacked on this one the text is moved outside. If *none*, no text appears.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `label` and `value`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the sample data to be binned on the x axis.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the sample data to be binned on the y axis.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Histogram2d([autobinx=], [autobiny=], [autocolorscale=], [bingroup=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [histfunc=], [histnorm=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [nbinsx=], [nbinsy=], [opacity=], [reversescale=], [showlegend=], [showscale=], [stream=], [textfont=], [texttemplate=], [transform=], [uid=], [uirevision=], [visible=], [x=], [xaxis=], [xbingroup=], [xbins=], [xcalendar=], [xgap=], [xhoverformat=], [xsrc=], [y=], [yaxis=], [ybingroup=], [ybins=], [ycalendar=], [ygap=], [yhoverformat=], [ysrc=], [z=], [zauto=], [zhoverformat=], [zmax=], [zmid=], [zmin=], [zsmooth=], [zsrc=]) → Histogram2d
Create a new ‘Histogram2d’ object
autobinx- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobinx` is not needed. However, we accept `autobinx: true` or `false` and will update `xbins` accordingly before deleting `autobinx` from the trace.autobiny- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobiny` is not needed. However, we accept `autobiny: true` or `false` and will update `ybins` accordingly before deleting `autobiny` from the trace.autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.bingroup- Set the `xbingroup` and `ybingroup` default prefix For example, setting a `bingroup` of *1* on two histogram2d traces will make them their x-bins and y-bins match separately.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.histfunc- Specifies the binning function used for this histogram trace. If *count*, the histogram values are computed by counting the number of values lying inside each bin. If *sum*, *avg*, *min*, *max*, the histogram values are computed using the sum, the average, the minimum or the maximum of the values lying inside each bin respectively.histnorm- Specifies the type of normalization used for this histogram trace. If **, the span of each bar corresponds to the number of occurrences (i.e. the number of data points lying inside the bins). If *percent* / *probability*, the span of each bar corresponds to the percentage / fraction of occurrences with respect to the total number of sample points (here, the sum of all bin HEIGHTS equals 100% / 1). If *density*, the span of each bar corresponds to the number of occurrences in a bin divided by the size of the bin interval (here, the sum of all bin AREAS equals the total number of sample points). If *probability density*, the area of each bar corresponds to the probability that an event will fall into the corresponding bin (here, the sum of all bin AREAS equals 1).hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `z` Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.nbinsx- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `xbins.size` is provided.nbinsy- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `ybins.size` is provided.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.textfont- Sets the text font.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `z`transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the sample data to be binned on the x axis.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xbingroup- Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value can be used to set (1D) histogram `bingroup`xcalendar- Sets the calendar system to use with `x` date data.xgap- Sets the horizontal gap (in pixels) between bricks.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the sample data to be binned on the y axis.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ybingroup- Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value can be used to set (1D) histogram `bingroup`ycalendar- Sets the calendar system to use with `y` date data.ygap- Sets the vertical gap (in pixels) between bricks.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the aggregation data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsmooth- Picks a smoothing algorithm use to smooth `z` data.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Histogram2dContour([autobinx=], [autobiny=], [autocolorscale=], [autocontour=], [bingroup=], [coloraxis=], [colorbar=], [colorscale=], [contours=], [customdata=], [customdatasrc=], [histfunc=], [histnorm=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [name=], [nbinsx=], [nbinsy=], [ncontours=], [opacity=], [reversescale=], [showlegend=], [showscale=], [stream=], [textfont=], [texttemplate=], [transform=], [uid=], [uirevision=], [visible=], [x=], [xaxis=], [xbingroup=], [xbins=], [xcalendar=], [xhoverformat=], [xsrc=], [y=], [yaxis=], [ybingroup=], [ybins=], [ycalendar=], [yhoverformat=], [ysrc=], [z=], [zauto=], [zhoverformat=], [zmax=], [zmid=], [zmin=], [zsrc=]) → Histogram2dContour
Create a new ‘Histogram2dContour’ object
autobinx- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobinx` is not needed. However, we accept `autobinx: true` or `false` and will update `xbins` accordingly before deleting `autobinx` from the trace.autobiny- Obsolete: since v1.42 each bin attribute is auto-determined separately and `autobiny` is not needed. However, we accept `autobiny: true` or `false` and will update `ybins` accordingly before deleting `autobiny` from the trace.autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.autocontour- Determines whether or not the contour level attributes are picked by an algorithm. If *true*, the number of contour levels can be set in `ncontours`. If *false*, set the contour level attributes in `contours`.bingroup- Set the `xbingroup` and `ybingroup` default prefix For example, setting a `bingroup` of *1* on two histogram2d traces will make them their x-bins and y-bins match separately.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `zmin` and `zmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.histfunc- Specifies the binning function used for this histogram trace. If *count*, the histogram values are computed by counting the number of values lying inside each bin. If *sum*, *avg*, *min*, *max*, the histogram values are computed using the sum, the average, the minimum or the maximum of the values lying inside each bin respectively.histnorm- Specifies the type of normalization used for this histogram trace. If **, the span of each bar corresponds to the number of occurrences (i.e. the number of data points lying inside the bins). If *percent* / *probability*, the span of each bar corresponds to the percentage / fraction of occurrences with respect to the total number of sample points (here, the sum of all bin HEIGHTS equals 100% / 1). If *density*, the span of each bar corresponds to the number of occurrences in a bin divided by the size of the bin interval (here, the sum of all bin AREAS equals the total number of sample points). If *probability density*, the area of each bar corresponds to the probability that an event will fall into the corresponding bin (here, the sum of all bin AREAS equals 1).hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variable `z` Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.nbinsx- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `xbins.size` is provided.nbinsy- Specifies the maximum number of desired bins. This value will be used in an algorithm that will decide the optimal bin size such that the histogram best visualizes the distribution of the data. Ignored if `ybins.size` is provided.ncontours- Sets the maximum number of contour levels. The actual number of contours will be chosen automatically to be less than or equal to the value of `ncontours`. Has an effect only if `autocontour` is *true* or if `contours.size` is missing.opacity- Sets the opacity of the trace.reversescale- Reverses the color mapping if true. If true, `zmin` will correspond to the last color in the array and `zmax` will correspond to the first color.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.textfont- For this trace it only has an effect if `coloring` is set to *heatmap*. Sets the text font.texttemplate- For this trace it only has an effect if `coloring` is set to *heatmap*. Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `x`, `y`, `z` and `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the sample data to be binned on the x axis.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xbingroup- Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value can be used to set (1D) histogram `bingroup`xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the sample data to be binned on the y axis.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ybingroup- Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value can be used to set (1D) histogram `bingroup`ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the aggregation data.zauto- Determines whether or not the color domain is computed with respect to the input data (here in `z`) or the bounds set in `zmin` and `zmax` Defaults to `false` when `zmin` and `zmax` are set by the user.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.zmax- Sets the upper bound of the color domain. Value should have the same units as in `z` and if set, `zmin` must be set as well.zmid- Sets the mid-point of the color domain by scaling `zmin` and/or `zmax` to be equidistant to this point. Value should have the same units as in `z`. Has no effect when `zauto` is `false`.zmin- Sets the lower bound of the color domain. Value should have the same units as in `z` and if set, `zmax` must be set as well.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Icicle([branchvalues=], [count=], [customdata=], [customdatasrc=], [domain=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextfont=], [labels=], [labelssrc=], [leaf=], [legendgrouptitle=], [legendrank=], [legendwidth=], [level=], [marker=], [maxdepth=], [meta=], [metasrc=], [name=], [opacity=], [outsidetextfont=], [parents=], [parentssrc=], [pathbar=], [root=], [sort=], [stream=], [text=], [textfont=], [textinfo=], [textposition=], [textsrc=], [texttemplate=], [texttemplatesrc=], [tiling=], [transform=], [uid=], [uirevision=], [values=], [valuessrc=], [visible=]) → Icicle
Create a new ‘Icicle’ object
branchvalues- Determines how the items in `values` are summed. When set to *total*, items in `values` are taken to be value of all its descendants. When set to *remainder*, items in `values` corresponding to the root and the branches sectors are taken to be the extra part not part of the sum of the values at their leaves.count- Determines default for `values` when it is not provided, by inferring a 1 for each of the *leaves* and/or *branches*, otherwise 0.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry` and `percentParent`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextfont- Sets the font used for `textinfo` lying inside the sector.labels- Sets the labels of each of the sectors.labelssrc- Sets the source reference on Chart Studio Cloud for `labels`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.level- Sets the level from which this trace hierarchy is rendered. Set `level` to `''` to start from the root node in the hierarchy. Must be an "id" if `ids` is filled in, otherwise plotly attempts to find a matching item in `labels`.maxdepth- Sets the number of rendered sectors from any given `level`. Set `maxdepth` to *-1* to render all the levels in the hierarchy.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.outsidetextfont- Sets the font used for `textinfo` lying outside the sector. This option refers to the root of the hierarchy presented on top left corner of a treemap graph. Please note that if a hierarchy has multiple root nodes, this option won't have any effect and `insidetextfont` would be used.parents- Sets the parent sectors for each of the sectors. Empty string items '' are understood to reference the root node in the hierarchy. If `ids` is filled, `parents` items are understood to be "ids" themselves. When `ids` is not set, plotly attempts to find matching items in `labels`, but beware they must be unique.parentssrc- Sets the source reference on Chart Studio Cloud for `parents`.sort- Determines whether or not the sectors are reordered from largest to smallest.text- Sets text elements associated with each sector. If trace `textinfo` contains a *text* flag, these elements will be seen on the chart. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the font used for `textinfo`.textinfo- Determines which trace information appear on the graph.textposition- Sets the positions of the `text` elements.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry`, `percentParent`, `label` and `value`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.values- Sets the values associated with each of the sectors. Use with `branchvalues` to determine how the values are summed.valuessrc- Sets the source reference on Chart Studio Cloud for `values`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Image([colormodel=], [customdata=], [customdatasrc=], [dx=], [dy=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [name=], [opacity=], [source=], [stream=], [text=], [textsrc=], [uid=], [uirevision=], [visible=], [x0=], [xaxis=], [y0=], [yaxis=], [z=], [zmax=], [zmin=], [zsmooth=], [zsrc=]) → Image
Create a new ‘Image’ object
colormodel- Color model used to map the numerical color components described in `z` into colors. If `source` is specified, this attribute will be set to `rgba256` otherwise it defaults to `rgb`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Set the pixel's horizontal size.dy- Set the pixel's vertical sizehoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `z`, `color` and `colormodel`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.source- Specifies the data URI of the image to be visualized. The URI consists of "data:image/[<media subtype>][;base64],<data>"text- Sets the text elements associated with each z value.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x0- Set the image's x position.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.y0- Set the image's y position.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.z- A 2-dimensional array in which each element is an array of 3 or 4 numbers representing a color.zmax- Array defining the higher bound for each color component. Note that the default value will depend on the colormodel. For the `rgb` colormodel, it is [255, 255, 255]. For the `rgba` colormodel, it is [255, 255, 255, 1]. For the `rgba256` colormodel, it is [255, 255, 255, 255]. For the `hsl` colormodel, it is [360, 100, 100]. For the `hsla` colormodel, it is [360, 100, 100, 1].zmin- Array defining the lower bound for each color component. Note that the default value will depend on the colormodel. For the `rgb` colormodel, it is [0, 0, 0]. For the `rgba` colormodel, it is [0, 0, 0, 0]. For the `rgba256` colormodel, it is [0, 0, 0, 0]. For the `hsl` colormodel, it is [0, 0, 0]. For the `hsla` colormodel, it is [0, 0, 0, 0].zsmooth- Picks a smoothing algorithm used to smooth `z` data. This only applies for image traces that use the `source` attribute.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Indicator([align=], [customdata=], [customdatasrc=], [delta=], [domain=], [gauge=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [mode=], [name=], [number=], [stream=], [title=], [transform=], [uid=], [uirevision=], [value=], [visible=]) → Indicator
Create a new ‘Indicator’ object
align- Sets the horizontal alignment of the `text` within the box. Note that this attribute has no effect if an angular gauge is displayed: in this case, it is always centeredcustomdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.gauge- The gauge of the Indicator plot.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines how the value is displayed on the graph. `number` displays the value numerically in text. `delta` displays the difference to a reference value in text. Finally, `gauge` displays the value graphically on an axis.name- Sets the trace name. The trace name appear as the legend item and on hover.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.value- Sets the number to be displayed.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Isosurface([autocolorscale=], [caps=], [cauto=], [cmax=], [cmid=], [cmin=], [coloraxis=], [colorbar=], [colorscale=], [contour=], [customdata=], [customdatasrc=], [flatshading=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [isomax=], [isomin=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [scene=], [showlegend=], [showscale=], [slices=], [spaceframe=], [stream=], [surface=], [text=], [textsrc=], [uid=], [uirevision=], [value=], [valuehoverformat=], [valuesrc=], [visible=], [x=], [xhoverformat=], [xsrc=], [y=], [yhoverformat=], [ysrc=], [z=], [zhoverformat=], [zsrc=]) → Isosurface
Create a new ‘Isosurface’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here `value`) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as `value` and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as `value`. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as `value` and if set, `cmax` must be set as well.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.flatshading- Determines whether or not normal smoothing is applied to the meshes, creating meshes with an angular, low-poly look via flat reflections.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.isomax- Sets the maximum boundary for iso-surface plot.isomin- Sets the minimum boundary for iso-surface plot.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with the vertices. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.value- Sets the 4th dimension (value) of the vertices.valuehoverformat- Sets the hover text formatting rulefor `value` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.valuesrc- Sets the source reference on Chart Studio Cloud for `value`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the X coordinates of the vertices on X axis.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the Y coordinates of the vertices on Y axis.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the Z coordinates of the vertices on Z axis.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Layout([_deprecated=], [activeselection=], [activeshape=], [annotation=], [autosize=], [autotypenumbers=], [calendar=], [clickmode=], [coloraxis=], [colorscale=], [colorway=], [computed=], [datarevision=], [dragmode=], [editrevision=], [font=], [geo=], [grid=], [height=], [hidesources=], [hoverdistance=], [hoverlabel=], [hovermode=], [image=], [legend=], [mapbox=], [margin=], [meta=], [metasrc=], [minreducedheight=], [minreducedwidth=], [modebar=], [newselection=], [newshape=], [paper_bgcolor=], [plot_bgcolor=], [polar=], [scene=], [selectdirection=], [selectionrevision=], [selection=], [separators=], [shape=], [showlegend=], [slider=], [smith=], [spikedistance=], [template=], [ternary=], [title=], [transition=], [uirevision=], [uniformtext=], [updatemenu=], [width=], [xaxis=], [yaxis=]) → Layout
Create a new ‘Layout’ object
autosize- Determines whether or not a layout width or height that has been left undefined by the user is initialized on each relayout. Note that, regardless of this attribute, an undefined layout width or height is always initialized on the first call to plot.autotypenumbers- Using *strict* a numeric string in trace data is not converted to a number. Using *convert types* a numeric string in trace data may be treated as a number during automatic axis `type` detection. This is the default value; however it could be overridden for individual axes.calendar- Sets the default calendar system to use for interpreting and displaying dates throughout the plot.clickmode- Determines the mode of single click interactions. *event* is the default value and emits the `plotly_click` event. In addition this mode emits the `plotly_selected` event in drag modes *lasso* and *select*, but with no event data attached (kept for compatibility reasons). The *select* flag enables selecting single data points via click. This mode also supports persistent selections, meaning that pressing Shift while clicking, adds to / subtracts from an existing selection. *select* with `hovermode`: *x* can be confusing, consider explicitly setting `hovermode`: *closest* when using this feature. Selection events are sent accordingly as long as *event* flag is set as well. When the *event* flag is missing, `plotly_click` and `plotly_selected` events are not fired.colorway- Sets the default trace colors.computed- Placeholder for exporting automargin-impacting values namely `margin.t`, `margin.b`, `margin.l` and `margin.r` in *full-json* mode.datarevision- If provided, a changed value tells `Plotly.react` that one or more data arrays has changed. This way you can modify arrays in-place rather than making a complete new copy for an incremental change. If NOT provided, `Plotly.react` assumes that data arrays are being treated as immutable, thus any data array with a different identity from its predecessor contains new data.dragmode- Determines the mode of drag interactions. *select* and *lasso* apply only to scatter traces with markers or text. *orbit* and *turntable* apply only to 3D scenes.editrevision- Controls persistence of user-driven changes in `editable: true` configuration, other than trace names and axis titles. Defaults to `layout.uirevision`.font- Sets the global font. Note that fonts used in traces and other layout components inherit from the global font.height- Sets the plot's height (in px).hidesources- Determines whether or not a text link citing the data source is placed at the bottom-right cored of the figure. Has only an effect only on graphs that have been generated via forked graphs from the Chart Studio Cloud (at https://chart-studio.plotly.com or on-premise).hoverdistance- Sets the default distance (in pixels) to look for data to add hover labels (-1 means no cutoff, 0 means no looking for data). This is only a real distance for hovering on point-like objects, like scatter points. For area-like objects (bars, scatter fills, etc) hovering is on inside the area and off outside, but these objects will not supersede hover on point-like objects in case of conflict.hovermode- Determines the mode of hover interactions. If *closest*, a single hoverlabel will appear for the *closest* point within the `hoverdistance`. If *x* (or *y*), multiple hoverlabels will appear for multiple points at the *closest* x- (or y-) coordinate within the `hoverdistance`, with the caveat that no more than one hoverlabel will appear per trace. If *x unified* (or *y unified*), a single hoverlabel will appear multiple points at the closest x- (or y-) coordinate within the `hoverdistance` with the caveat that no more than one hoverlabel will appear per trace. In this mode, spikelines are enabled by default perpendicular to the specified axis. If false, hover interactions are disabled.meta- Assigns extra meta information that can be used in various `text` attributes. Attributes such as the graph, axis and colorbar `title.text`, annotation `text` `trace.name` in legend items, `rangeselector`, `updatemenus` and `sliders` `label` text all support `meta`. One can access `meta` fields using template strings: `%{meta[i]}` where `i` is the index of the `meta` item in question. `meta` can also be an object for example `{key: value}` which can be accessed %{meta[key]}.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.minreducedheight- Minimum height of the plot with margin.automargin applied (in px)minreducedwidth- Minimum width of the plot with margin.automargin applied (in px)paper_bgcolor- Sets the background color of the paper where the graph is drawn.plot_bgcolor- Sets the background color of the plotting area in-between x and y axes.selectdirection- When `dragmode` is set to *select*, this limits the selection of the drag to horizontal, vertical or diagonal. *h* only allows horizontal selection, *v* only vertical, *d* only diagonal and *any* sets no limit.selectionrevision- Controls persistence of user-driven changes in selected points from all traces.separators- Sets the decimal and thousand separators. For example, *. * puts a '.' before decimals and a space between thousands. In English locales, dflt is *.,* but other locales may alter this default.showlegend- Determines whether or not a legend is drawn. Default is `true` if there is a trace to show and any of these: a) Two or more traces would by default be shown in the legend. b) One pie trace is shown in the legend. c) One trace is explicitly given with `showlegend: true`.spikedistance- Sets the default distance (in pixels) to look for data to draw spikelines to (-1 means no cutoff, 0 means no looking for data). As with hoverdistance, distance does not apply to area-like objects. In addition, some objects can be hovered on but will not generate spikelines, such as scatter fills.template- Default attributes to be applied to the plot. Templates can be created from existing plots using `Plotly.makeTemplate`, or created manually. They should be objects with format: `{layout: layoutTemplate, data: {[type]: [traceTemplate, ...]}, ...}` `layoutTemplate` and `traceTemplate` are objects matching the attribute structure of `layout` and a data trace. Trace templates are applied cyclically to traces of each type. Container arrays (eg `annotations`) have special handling: An object ending in `defaults` (eg `annotationdefaults`) is applied to each array item. But if an item has a `templateitemname` key we look in the template array for an item with matching `name` and apply that instead. If no matching `name` is found we mark the item invisible. Any named template item not referenced is appended to the end of the array, so you can use this for a watermark annotation or a logo image, for example. To omit one of these items on the plot, make an item with matching `templateitemname` and `visible: false`.transition- Sets transition options used during Plotly.react updates.uirevision- Used to allow user interactions with the plot to persist after `Plotly.react` calls that are unaware of these interactions. If `uirevision` is omitted, or if it is given and it changed from the previous `Plotly.react` call, the exact new figure is used. If `uirevision` is truthy and did NOT change, any attribute that has been affected by user interactions and did not receive a different value in the new figure will keep the interaction value. `layout.uirevision` attribute serves as the default for `uirevision` attributes in various sub-containers. For finer control you can set these sub-attributes directly. For example, if your app separately controls the data on the x and y axes you might set `xaxis.uirevision=*time*` and `yaxis.uirevision=*cost*`. Then if only the y data is changed, you can update `yaxis.uirevision=*quantity*` and the y axis range will reset but the x axis range will retain any user-driven zoom.width- Sets the plot's width (in px).
plotly.graph_objs.Mesh3d([alphahull=], [autocolorscale=], [cauto=], [cmax=], [cmid=], [cmin=], [color=], [coloraxis=], [colorbar=], [colorscale=], [contour=], [customdata=], [customdatasrc=], [delaunayaxis=], [facecolor=], [facecolorsrc=], [flatshading=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [i=], [ids=], [idssrc=], [intensity=], [intensitymode=], [intensitysrc=], [isrc=], [j=], [jsrc=], [k=], [ksrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [scene=], [showlegend=], [showscale=], [stream=], [text=], [textsrc=], [uid=], [uirevision=], [vertexcolor=], [vertexcolorsrc=], [visible=], [x=], [xcalendar=], [xhoverformat=], [xsrc=], [y=], [ycalendar=], [yhoverformat=], [ysrc=], [z=], [zcalendar=], [zhoverformat=], [zsrc=]) → Mesh3d
Create a new ‘Mesh3d’ object
alphahull- Determines how the mesh surface triangles are derived from the set of vertices (points) represented by the `x`, `y` and `z` arrays, if the `i`, `j`, `k` arrays are not supplied. For general use of `mesh3d` it is preferred that `i`, `j`, `k` are supplied. If *-1*, Delaunay triangulation is used, which is mainly suitable if the mesh is a single, more or less layer surface that is perpendicular to `delaunayaxis`. In case the `delaunayaxis` intersects the mesh surface at more than one point it will result triangles that are very long in the dimension of `delaunayaxis`. If *>0*, the alpha-shape algorithm is used. In this case, the positive `alphahull` value signals the use of the alpha-shape algorithm, _and_ its value acts as the parameter for the mesh fitting. If *0*, the convex-hull algorithm is used. It is suitable for convex bodies or if the intention is to enclose the `x`, `y` and `z` point set into a convex hull.autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here `intensity`) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as `intensity` and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as `intensity`. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as `intensity` and if set, `cmax` must be set as well.color- Sets the color of the whole meshcoloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.delaunayaxis- Sets the Delaunay axis, which is the axis that is perpendicular to the surface of the Delaunay triangulation. It has an effect if `i`, `j`, `k` are not provided and `alphahull` is set to indicate Delaunay triangulation.facecolor- Sets the color of each face Overrides *color* and *vertexcolor*.facecolorsrc- Sets the source reference on Chart Studio Cloud for `facecolor`.flatshading- Determines whether or not normal smoothing is applied to the meshes, creating meshes with an angular, low-poly look via flat reflections.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.i- A vector of vertex indices, i.e. integer values between 0 and the length of the vertex vectors, representing the *first* vertex of a triangle. For example, `{i[m], j[m], k[m]}` together represent face m (triangle m) in the mesh, where `i[m] = n` points to the triplet `{x[n], y[n], z[n]}` in the vertex arrays. Therefore, each element in `i` represents a point in space, which is the first vertex of a triangle.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.intensity- Sets the intensity values for vertices or cells as defined by `intensitymode`. It can be used for plotting fields on meshes.intensitymode- Determines the source of `intensity` values.intensitysrc- Sets the source reference on Chart Studio Cloud for `intensity`.isrc- Sets the source reference on Chart Studio Cloud for `i`.j- A vector of vertex indices, i.e. integer values between 0 and the length of the vertex vectors, representing the *second* vertex of a triangle. For example, `{i[m], j[m], k[m]}` together represent face m (triangle m) in the mesh, where `j[m] = n` points to the triplet `{x[n], y[n], z[n]}` in the vertex arrays. Therefore, each element in `j` represents a point in space, which is the second vertex of a triangle.jsrc- Sets the source reference on Chart Studio Cloud for `j`.k- A vector of vertex indices, i.e. integer values between 0 and the length of the vertex vectors, representing the *third* vertex of a triangle. For example, `{i[m], j[m], k[m]}` together represent face m (triangle m) in the mesh, where `k[m] = n` points to the triplet `{x[n], y[n], z[n]}` in the vertex arrays. Therefore, each element in `k` represents a point in space, which is the third vertex of a triangle.ksrc- Sets the source reference on Chart Studio Cloud for `k`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with the vertices. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.vertexcolor- Sets the color of each vertex Overrides *color*. While Red, green and blue colors are in the range of 0 and 255; in the case of having vertex color data in RGBA format, the alpha color should be normalized to be between 0 and 1.vertexcolorsrc- Sets the source reference on Chart Studio Cloud for `vertexcolor`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the X coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the Y coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the Z coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.zcalendar- Sets the calendar system to use with `z` date data.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Ohlc([close=], [closesrc=], [customdata=], [customdatasrc=], [decreasing=], [high=], [highsrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [increasing=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [low=], [lowsrc=], [meta=], [metasrc=], [name=], [opacity=], [open=], [opensrc=], [selectedpoints=], [showlegend=], [stream=], [text=], [textsrc=], [tickwidth=], [transform=], [uid=], [uirevision=], [visible=], [x=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [yaxis=], [yhoverformat=]) → Ohlc
Create a new ‘Ohlc’ object
close- Sets the close values.closesrc- Sets the source reference on Chart Studio Cloud for `close`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.high- Sets the high values.highsrc- Sets the source reference on Chart Studio Cloud for `high`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.low- Sets the low values.lowsrc- Sets the source reference on Chart Studio Cloud for `low`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.open- Sets the open values.opensrc- Sets the source reference on Chart Studio Cloud for `open`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets hover text elements associated with each sample point. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to this trace's sample points.textsrc- Sets the source reference on Chart Studio Cloud for `text`.tickwidth- Sets the width of the open/close tick marks relative to the *x* minimal interval.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates. If absent, linear coordinate will be generated.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.
plotly.graph_objs.Parcats([arrangement=], [bundlecolors=], [counts=], [countssrc=], [dimension=], [domain=], [hoverinfo=], [hoveron=], [hovertemplate=], [labelfont=], [legendgrouptitle=], [legendwidth=], [line=], [meta=], [metasrc=], [name=], [sortpaths=], [stream=], [tickfont=], [transform=], [uid=], [uirevision=], [visible=]) → Parcats
Create a new ‘Parcats’ object
arrangement- Sets the drag interaction mode for categories and dimensions. If `perpendicular`, the categories can only move along a line perpendicular to the paths. If `freeform`, the categories can freely move on the plane. If `fixed`, the categories and dimensions are stationary.bundlecolors- Sort paths so that like colors are bundled together within each category.counts- The number of observations represented by each state. Defaults to 1 so that each state represents one observationcountssrc- Sets the source reference on Chart Studio Cloud for `counts`.dimension- The dimensions (variables) of the parallel categories diagram.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoveron- Sets the hover interaction mode for the parcats diagram. If `category`, hover interaction take place per category. If `color`, hover interactions take place per color per category. If `dimension`, hover interactions take place across all categories per dimension.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `count`, `probability`, `category`, `categorycount`, `colorcount` and `bandcolorcount`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.labelfont- Sets the font for the `dimension` labels.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.sortpaths- Sets the path sorting algorithm. If `forward`, sort paths based on dimension categories from left to right. If `backward`, sort paths based on dimensions categories from right to left.tickfont- Sets the font for the `category` labels.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Parcoords([customdata=], [customdatasrc=], [dimension=], [domain=], [ids=], [idssrc=], [labelangle=], [labelfont=], [labelside=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [meta=], [metasrc=], [name=], [rangefont=], [stream=], [tickfont=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Parcoords
Create a new ‘Parcoords’ object
customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dimension- The dimensions (variables) of the parallel coordinates chart. 2..60 dimensions are supported.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.labelangle- Sets the angle of the labels with respect to the horizontal. For example, a `tickangle` of -90 draws the labels vertically. Tilted labels with *labelangle* may be positioned better inside margins when `labelposition` is set to *bottom*.labelfont- Sets the font for the `dimension` labels.labelside- Specifies the location of the `label`. *top* positions labels above, next to the title *bottom* positions labels below the graph Tilted labels with *labelangle* may be positioned better inside margins when `labelposition` is set to *bottom*.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.rangefont- Sets the font for the `dimension` range values.tickfont- Sets the font for the `dimension` tick values.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Pie([_deprecated=], [automargin=], [customdata=], [customdatasrc=], [direction=], [dlabel=], [domain=], [hole=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextfont=], [insidetextorientation=], [label0=], [labels=], [labelssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [opacity=], [outsidetextfont=], [pull=], [pullsrc=], [rotation=], [scalegroup=], [showlegend=], [sort=], [stream=], [text=], [textfont=], [textinfo=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [title=], [transform=], [uid=], [uirevision=], [values=], [valuessrc=], [visible=]) → Pie
Create a new ‘Pie’ object
automargin- Determines whether outside text labels can push the margins.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.direction- Specifies the direction at which succeeding sectors follow one another.dlabel- Sets the label step. See `label0` for more info.hole- Sets the fraction of the radius to cut out of the pie. Use this to make a donut chart.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `label`, `color`, `value`, `percent` and `text`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextfont- Sets the font used for `textinfo` lying inside the sector.insidetextorientation- Controls the orientation of the text inside chart sectors. When set to *auto*, text may be oriented in any direction in order to be as big as possible in the middle of a sector. The *horizontal* option orients text to be parallel with the bottom of the chart, and may make text smaller in order to achieve that goal. The *radial* option orients text along the radius of the sector. The *tangential* option orients text perpendicular to the radius of the sector.label0- Alternate to `labels`. Builds a numeric set of labels. Use with `dlabel` where `label0` is the starting label and `dlabel` the step.labels- Sets the sector labels. If `labels` entries are duplicated, we sum associated `values` or simply count occurrences if `values` is not provided. For other array attributes (including color) we use the first non-empty entry among all occurrences of the label.labelssrc- Sets the source reference on Chart Studio Cloud for `labels`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.outsidetextfont- Sets the font used for `textinfo` lying outside the sector.pull- Sets the fraction of larger radius to pull the sectors out from the center. This can be a constant to pull all slices apart from each other equally or an array to highlight one or more slices.pullsrc- Sets the source reference on Chart Studio Cloud for `pull`.rotation- Instead of the first slice starting at 12 o'clock, rotate to some other angle.scalegroup- If there are multiple pie charts that should be sized according to their totals, link them by providing a non-empty group id here shared by every trace in the same group.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.sort- Determines whether or not the sectors are reordered from largest to smallest.text- Sets text elements associated with each sector. If trace `textinfo` contains a *text* flag, these elements will be seen on the chart. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the font used for `textinfo`.textinfo- Determines which trace information appear on the graph.textposition- Specifies the location of the `textinfo`.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `label`, `color`, `value`, `percent` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.values- Sets the values of the sectors. If omitted, we count occurrences of each label.valuessrc- Sets the source reference on Chart Studio Cloud for `values`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Pointcloud([customdata=], [customdatasrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [ids=], [idssrc=], [indices=], [indicessrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [opacity=], [showlegend=], [stream=], [text=], [textsrc=], [uid=], [uirevision=], [visible=], [x=], [xaxis=], [xbounds=], [xboundssrc=], [xsrc=], [xy=], [xysrc=], [y=], [yaxis=], [ybounds=], [yboundssrc=], [ysrc=]) → Pointcloud
Create a new ‘Pointcloud’ object
customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.indices- A sequential value, 0..n, supply it to avoid creating this array inside plotting. If specified, it must be a typed `Int32Array` array. Its length must be equal to or greater than the number of points. For the best performance and memory use, create one large `indices` typed array that is guaranteed to be at least as long as the largest number of points during use, and reuse it on each `Plotly.restyle()` call.indicessrc- Sets the source reference on Chart Studio Cloud for `indices`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xbounds- Specify `xbounds` in the shape of `[xMin, xMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `ybounds` for the performance benefits.xboundssrc- Sets the source reference on Chart Studio Cloud for `xbounds`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.xy- Faster alternative to specifying `x` and `y` separately. If supplied, it must be a typed `Float32Array` array that represents points such that `xy[i * 2] = x[i]` and `xy[i * 2 + 1] = y[i]`xysrc- Sets the source reference on Chart Studio Cloud for `xy`.y- Sets the y coordinates.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ybounds- Specify `ybounds` in the shape of `[yMin, yMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `xbounds` for the performance benefits.yboundssrc- Sets the source reference on Chart Studio Cloud for `ybounds`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Sankey([arrangement=], [customdata=], [customdatasrc=], [domain=], [hoverinfo=], [hoverlabel=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [link=], [meta=], [metasrc=], [name=], [node=], [orientation=], [selectedpoints=], [stream=], [textfont=], [uid=], [uirevision=], [valueformat=], [valuesuffix=], [visible=]) → Sankey
Create a new ‘Sankey’ object
arrangement- If value is `snap` (the default), the node arrangement is assisted by automatic snapping of elements to preserve space between nodes specified via `nodepad`. If value is `perpendicular`, the nodes can only move along a line perpendicular to the flow. If value is `freeform`, the nodes can freely move on the plane. If value is `fixed`, the nodes are stationary.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. Note that this attribute is superseded by `node.hoverinfo` and `node.hoverinfo` for nodes and links respectively.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.link- The links of the Sankey plot.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.node- The nodes of the Sankey plot.orientation- Sets the orientation of the Sankey diagram.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.textfont- Sets the font for node labelsuid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.valueformat- Sets the value formatting rule using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.valuesuffix- Adds a unit to follow the value in the hover tooltip. Add a space if a separation is necessary from the value.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scatter([alignmentgroup=], [cliponaxis=], [connectgaps=], [customdata=], [customdatasrc=], [dx=], [dy=], [error_x=], [error_y=], [fill=], [fillcolor=], [fillpattern=], [groupnorm=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [offsetgroup=], [opacity=], [orientation=], [selected=], [selectedpoints=], [showlegend=], [stackgaps=], [stackgroup=], [stream=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [x=], [x0=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [ycalendar=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Scatter
Create a new ‘Scatter’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.cliponaxis- Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.fill- Sets the area to fill with a solid color. Defaults to *none* unless this trace is stacked, then it gets *tonexty* (*tonextx*) if `orientation` is *v* (*h*) Use with `fillcolor` if not *none*. *tozerox* and *tozeroy* fill to x=0 and y=0 respectively. *tonextx* and *tonexty* fill between the endpoints of this trace and the endpoints of the trace before it, connecting those endpoints with straight lines (to make a stacked area graph); if there is no trace before it, they behave like *tozerox* and *tozeroy*. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other. Traces in a `stackgroup` will only fill to (or be filled to) other traces in the same group. With multiple `stackgroup`s or some traces stacked and some not, if fill-linked traces are not already consecutive, the later ones will be pushed down in the drawing order.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.fillpattern- Sets the pattern within the marker.groupnorm- Only relevant when `stackgroup` is used, and only the first `groupnorm` found in the `stackgroup` will be used - including if `visible` is *legendonly* but not if it is `false`. Sets the normalization for the sum of this `stackgroup`. With *fraction*, the value of each trace at each location is divided by the sum of all trace values at that location. *percent* is the same but multiplied by 100 to show percentages. If there are multiple subplots, or multiple `stackgroup`s on one subplot, each will be normalized within its own set.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is *toself* or *tonext* and there are no markers or text, then the default is *fills*, otherwise it is *points*.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.opacity- Sets the opacity of the trace.orientation- Only relevant in the following cases: 1. when `scattermode` is set to *group*. 2. when `stackgroup` is used, and only the first `orientation` found in the `stackgroup` will be used - including if `visible` is *legendonly* but not if it is `false`. Sets the stacking direction. With *v* (*h*), the y (x) values of subsequent traces are added. Also affects the default value of `fill`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.stackgaps- Only relevant when `stackgroup` is used, and only the first `stackgaps` found in the `stackgroup` will be used - including if `visible` is *legendonly* but not if it is `false`. Determines how we handle locations at which other traces in this group have data but this one does not. With *infer zero* we insert a zero at these locations. With *interpolate* we linearly interpolate between existing values, and extrapolate a constant beyond the existing values.stackgroup- Set several scatter traces (on the same subplot) to the same stackgroup in order to add their y values (or their x values if `orientation` is *h*). If blank or omitted this trace will not be stacked. Stacking also turns `fill` on by default, using *tonexty* (*tonextx*) if `orientation` is *h* (*v*) and sets the default `mode` to *lines* irrespective of point count. You can only stack on a numeric (linear or log) axis. Traces in a `stackgroup` will only fill to (or be filled to) other traces in the same group. With multiple `stackgroup`s or some traces stacked and some not, if fill-linked traces are not already consecutive, the later ones will be pushed down in the drawing order.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Scatter3d([connectgaps=], [customdata=], [customdatasrc=], [error_x=], [error_y=], [error_z=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [projection=], [scene=], [showlegend=], [stream=], [surfaceaxis=], [surfacecolor=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [visible=], [x=], [xcalendar=], [xhoverformat=], [xsrc=], [y=], [ycalendar=], [yhoverformat=], [ysrc=], [z=], [zcalendar=], [zhoverformat=], [zsrc=]) → Scatter3d
Create a new ‘Scatter3d’ object
connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets text elements associated with each (x,y,z) triplet. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y,z) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.surfaceaxis- If *-1*, the scatter points are not fill with a surface If *0*, *1*, *2*, the scatter points are filled with a Delaunay surface about the x, y, z respectively.surfacecolor- Sets the surface fill color.text- Sets text elements associated with each (x,y,z) triplet. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y,z) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the z coordinates.zcalendar- Sets the calendar system to use with `z` date data.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Scattercarpet([a=], [asrc=], [b=], [bsrc=], [carpet=], [connectgaps=], [customdata=], [customdatasrc=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [xaxis=], [yaxis=]) → Scattercarpet
Create a new ‘Scattercarpet’ object
a- Sets the a-axis coordinates.asrc- Sets the source reference on Chart Studio Cloud for `a`.b- Sets the b-axis coordinates.bsrc- Sets the source reference on Chart Studio Cloud for `b`.carpet- An identifier for this carpet, so that `scattercarpet` and `contourcarpet` traces can specify a carpet plot on which they lieconnectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. scatterternary has a subset of the options available to scatter. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is *toself* or *tonext* and there are no markers or text, then the default is *fills*, otherwise it is *points*.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (a,b) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b). To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (a,b) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b). If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `a`, `b` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
plotly.graph_objs.Scattergeo([connectgaps=], [customdata=], [customdatasrc=], [featureidkey=], [fill=], [fillcolor=], [geo=], [geojson=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [lat=], [latsrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [locationmode=], [locations=], [locationssrc=], [lon=], [lonsrc=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scattergeo
Create a new ‘Scattergeo’ object
connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.featureidkey- Sets the key in GeoJSON features which is used as id to match the items included in the `locations` array. Only has an effect when `geojson` is set. Support nested property, for example *properties.name*.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.geo- Sets a reference between this trace's geospatial coordinates and a geographic map. If *geo* (the default value), the geospatial coordinates refer to `layout.geo`. If *geo2*, the geospatial coordinates refer to `layout.geo2`, and so on.geojson- Sets optional GeoJSON data associated with this trace. If not given, the features on the base map are used when `locations` is set. It can be set as a valid GeoJSON object or as a URL string. Note that we only accept GeoJSONs of type *FeatureCollection* or *Feature* with geometries of type *Polygon* or *MultiPolygon*.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (lon,lat) pair or item in `locations`. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) or `locations` coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.lat- Sets the latitude coordinates (in degrees North).latsrc- Sets the source reference on Chart Studio Cloud for `lat`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.locationmode- Determines the set of locations used to match entries in `locations` to regions on the map. Values *ISO-3*, *USA-states*, *country names* correspond to features on the base map and value *geojson-id* corresponds to features from a custom GeoJSON linked to the `geojson` attribute.locations- Sets the coordinates via location IDs or names. Coordinates correspond to the centroid of each location given. See `locationmode` for more info.locationssrc- Sets the source reference on Chart Studio Cloud for `locations`.lon- Sets the longitude coordinates (in degrees East).lonsrc- Sets the source reference on Chart Studio Cloud for `lon`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (lon,lat) pair or item in `locations`. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) or `locations` coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `lat`, `lon`, `location` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scattergl([connectgaps=], [customdata=], [customdatasrc=], [dx=], [dy=], [error_x=], [error_y=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [stream=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [x=], [x0=], [xaxis=], [xcalendar=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [ycalendar=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Scattergl
Create a new ‘Scattergl’ object
connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.fill- Sets the area to fill with a solid color. Defaults to *none* unless this trace is stacked, then it gets *tonexty* (*tonextx*) if `orientation` is *v* (*h*) Use with `fillcolor` if not *none*. *tozerox* and *tozeroy* fill to x=0 and y=0 respectively. *tonextx* and *tonexty* fill between the endpoints of this trace and the endpoints of the trace before it, connecting those endpoints with straight lines (to make a stacked area graph); if there is no trace before it, they behave like *tozerox* and *tozeroy*. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other. Traces in a `stackgroup` will only fill to (or be filled to) other traces in the same group. With multiple `stackgroup`s or some traces stacked and some not, if fill-linked traces are not already consecutive, the later ones will be pushed down in the drawing order.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Scattermapbox([below=], [cluster=], [connectgaps=], [customdata=], [customdatasrc=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [lat=], [latsrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [lon=], [lonsrc=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [text=], [textfont=], [textposition=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scattermapbox
Create a new ‘Scattermapbox’ object
below- Determines if this scattermapbox trace's layers are to be inserted before the layer with the specified ID. By default, scattermapbox layers are inserted above all the base layers. To place the scattermapbox layers above every other layer, set `below` to *''*.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (lon,lat) pair If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.lat- Sets the latitude coordinates (in degrees North).latsrc- Sets the source reference on Chart Studio Cloud for `lat`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.lon- Sets the longitude coordinates (in degrees East).lonsrc- Sets the source reference on Chart Studio Cloud for `lon`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a mapbox subplot. If *mapbox* (the default value), the data refer to `layout.mapbox`. If *mapbox2*, the data refer to `layout.mapbox2`, and so on.text- Sets text elements associated with each (lon,lat) pair If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (lon,lat) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the icon text font (color=mapbox.layer.paint.text-color, size=mapbox.layer.layout.text-size). Has an effect only when `type` is set to *symbol*.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `lat`, `lon` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scatterpolar([cliponaxis=], [connectgaps=], [customdata=], [customdatasrc=], [dr=], [dtheta=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [r=], [r0=], [rsrc=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [theta=], [theta0=], [thetasrc=], [thetaunit=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scatterpolar
Create a new ‘Scatterpolar’ object
cliponaxis- Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dr- Sets the r coordinate step.dtheta- Sets the theta coordinate step. By default, the `dtheta` step equals the subplot's period divided by the length of the `r` coordinates.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. scatterpolar has a subset of the options available to scatter. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is *toself* or *tonext* and there are no markers or text, then the default is *fills*, otherwise it is *points*.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.r- Sets the radial coordinatesr0- Alternate to `r`. Builds a linear space of r coordinates. Use with `dr` where `r0` is the starting coordinate and `dr` the step.rsrc- Sets the source reference on Chart Studio Cloud for `r`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a polar subplot. If *polar* (the default value), the data refer to `layout.polar`. If *polar2*, the data refer to `layout.polar2`, and so on.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `r`, `theta` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.theta- Sets the angular coordinatestheta0- Alternate to `theta`. Builds a linear space of theta coordinates. Use with `dtheta` where `theta0` is the starting coordinate and `dtheta` the step.thetasrc- Sets the source reference on Chart Studio Cloud for `theta`.thetaunit- Sets the unit of input *theta* values. Has an effect only when on *linear* angular axes.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scatterpolargl([connectgaps=], [customdata=], [customdatasrc=], [dr=], [dtheta=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [r=], [r0=], [rsrc=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [theta=], [theta0=], [thetasrc=], [thetaunit=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scatterpolargl
Create a new ‘Scatterpolargl’ object
connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dr- Sets the r coordinate step.dtheta- Sets the theta coordinate step. By default, the `dtheta` step equals the subplot's period divided by the length of the `r` coordinates.fill- Sets the area to fill with a solid color. Defaults to *none* unless this trace is stacked, then it gets *tonexty* (*tonextx*) if `orientation` is *v* (*h*) Use with `fillcolor` if not *none*. *tozerox* and *tozeroy* fill to x=0 and y=0 respectively. *tonextx* and *tonexty* fill between the endpoints of this trace and the endpoints of the trace before it, connecting those endpoints with straight lines (to make a stacked area graph); if there is no trace before it, they behave like *tozerox* and *tozeroy*. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other. Traces in a `stackgroup` will only fill to (or be filled to) other traces in the same group. With multiple `stackgroup`s or some traces stacked and some not, if fill-linked traces are not already consecutive, the later ones will be pushed down in the drawing order.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.r- Sets the radial coordinatesr0- Alternate to `r`. Builds a linear space of r coordinates. Use with `dr` where `r0` is the starting coordinate and `dr` the step.rsrc- Sets the source reference on Chart Studio Cloud for `r`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a polar subplot. If *polar* (the default value), the data refer to `layout.polar`. If *polar2*, the data refer to `layout.polar2`, and so on.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `r`, `theta` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.theta- Sets the angular coordinatestheta0- Alternate to `theta`. Builds a linear space of theta coordinates. Use with `dtheta` where `theta0` is the starting coordinate and `dtheta` the step.thetasrc- Sets the source reference on Chart Studio Cloud for `theta`.thetaunit- Sets the unit of input *theta* values. Has an effect only when on *linear* angular axes.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scattersmith([cliponaxis=], [connectgaps=], [customdata=], [customdatasrc=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [imag=], [imagsrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [real=], [realsrc=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scattersmith
Create a new ‘Scattersmith’ object
cliponaxis- Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. scattersmith has a subset of the options available to scatter. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is *toself* or *tonext* and there are no markers or text, then the default is *fills*, otherwise it is *points*.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.imag- Sets the imaginary component of the data, in units of normalized impedance such that real=1, imag=0 is the center of the chart.imagsrc- Sets the source reference on Chart Studio Cloud for `imag`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.real- Sets the real component of the data, in units of normalized impedance such that real=1, imag=0 is the center of the chart.realsrc- Sets the source reference on Chart Studio Cloud for `real`.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a smith subplot. If *smith* (the default value), the data refer to `layout.smith`. If *smith2*, the data refer to `layout.smith2`, and so on.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `real`, `imag` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Scatterternary([a=], [asrc=], [b=], [bsrc=], [c=], [cliponaxis=], [connectgaps=], [csrc=], [customdata=], [customdatasrc=], [fill=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meta=], [metasrc=], [mode=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [stream=], [subplot=], [sum=], [text=], [textfont=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=]) → Scatterternary
Create a new ‘Scatterternary’ object
a- Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`.asrc- Sets the source reference on Chart Studio Cloud for `a`.b- Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`.bsrc- Sets the source reference on Chart Studio Cloud for `b`.c- Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`.cliponaxis- Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.csrc- Sets the source reference on Chart Studio Cloud for `c`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.fill- Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. scatterternary has a subset of the options available to scatter. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is *toself* or *tonext* and there are no markers or text, then the default is *fills*, otherwise it is *points*.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.mode- Determines the drawing mode for this scatter trace. If the provided `mode` includes *text* then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is *lines+markers*. Otherwise, *lines*.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.subplot- Sets a reference between this trace's data coordinates and a ternary subplot. If *ternary* (the default value), the data refer to `layout.ternary`. If *ternary2*, the data refer to `layout.ternary2`, and so on.sum- The number each triplet should sum to, if only two of `a`, `b`, and `c` are provided. This overrides `ternary<i>.sum` to normalize this specific trace, but does not affect the values displayed on the axes. 0 (or missing) means to use ternary<i>.sumtext- Sets text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the text font.textposition- Sets the positions of the `text` elements with respects to the (x,y) coordinates.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `a`, `b`, `c` and `text`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Splom([customdata=], [customdatasrc=], [diagonal=], [dimension=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [marker=], [meta=], [metasrc=], [name=], [opacity=], [selected=], [selectedpoints=], [showlegend=], [showlowerhalf=], [showupperhalf=], [stream=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [xaxes=], [xhoverformat=], [yaxes=], [yhoverformat=]) → Splom
Create a new ‘Splom’ object
customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showlowerhalf- Determines whether or not subplots on the lower half from the diagonal are displayed.showupperhalf- Determines whether or not subplots on the upper half from the diagonal are displayed.text- Sets text elements associated with each (x,y) pair to appear on hover. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).xaxes- Sets the list of x axes corresponding to dimensions of this splom trace. By default, a splom will match the first N xaxes where N is the number of input dimensions. Note that, in case where `diagonal.visible` is false and `showupperhalf` or `showlowerhalf` is false, this splom trace will generate one less x-axis and one less y-axis.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.yaxes- Sets the list of y axes corresponding to dimensions of this splom trace. By default, a splom will match the first N yaxes where N is the number of input dimensions. Note that, in case where `diagonal.visible` is false and `showupperhalf` or `showlowerhalf` is false, this splom trace will generate one less x-axis and one less y-axis.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.
plotly.graph_objs.Streamtube([autocolorscale=], [cauto=], [cmax=], [cmid=], [cmin=], [coloraxis=], [colorbar=], [colorscale=], [customdata=], [customdatasrc=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [maxdisplayed=], [meta=], [metasrc=], [name=], [opacity=], [reversescale=], [scene=], [showlegend=], [showscale=], [sizeref=], [starts=], [stream=], [text=], [u=], [uhoverformat=], [uid=], [uirevision=], [usrc=], [v=], [vhoverformat=], [visible=], [vsrc=], [w=], [whoverformat=], [wsrc=], [x=], [xhoverformat=], [xsrc=], [y=], [yhoverformat=], [ysrc=], [z=], [zhoverformat=], [zsrc=]) → Streamtube
Create a new ‘Streamtube’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here u/v/w norm) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as u/v/w norm and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as u/v/w norm. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as u/v/w norm and if set, `cmax` must be set as well.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `tubex`, `tubey`, `tubez`, `tubeu`, `tubev`, `tubew`, `norm` and `divergence`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.maxdisplayed- The maximum number of displayed segments in a streamtube.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.sizeref- The scaling factor for the streamtubes. The default is 1, which avoids two max divergence tubes from touching at adjacent starting positions.text- Sets a text element associated with this trace. If trace `hoverinfo` contains a *text* flag, this text element will be seen in all hover labels. Note that streamtube traces do not support array `text` values.u- Sets the x components of the vector field.uhoverformat- Sets the hover text formatting rulefor `u` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.usrc- Sets the source reference on Chart Studio Cloud for `u`.v- Sets the y components of the vector field.vhoverformat- Sets the hover text formatting rulefor `v` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).vsrc- Sets the source reference on Chart Studio Cloud for `v`.w- Sets the z components of the vector field.whoverformat- Sets the hover text formatting rulefor `w` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.wsrc- Sets the source reference on Chart Studio Cloud for `w`.x- Sets the x coordinates of the vector field.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates of the vector field.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the z coordinates of the vector field.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Sunburst([branchvalues=], [count=], [customdata=], [customdatasrc=], [domain=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextfont=], [insidetextorientation=], [labels=], [labelssrc=], [leaf=], [legendgrouptitle=], [legendrank=], [legendwidth=], [level=], [marker=], [maxdepth=], [meta=], [metasrc=], [name=], [opacity=], [outsidetextfont=], [parents=], [parentssrc=], [root=], [rotation=], [sort=], [stream=], [text=], [textfont=], [textinfo=], [textsrc=], [texttemplate=], [texttemplatesrc=], [transform=], [uid=], [uirevision=], [values=], [valuessrc=], [visible=]) → Sunburst
Create a new ‘Sunburst’ object
branchvalues- Determines how the items in `values` are summed. When set to *total*, items in `values` are taken to be value of all its descendants. When set to *remainder*, items in `values` corresponding to the root and the branches sectors are taken to be the extra part not part of the sum of the values at their leaves.count- Determines default for `values` when it is not provided, by inferring a 1 for each of the *leaves* and/or *branches*, otherwise 0.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry` and `percentParent`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextfont- Sets the font used for `textinfo` lying inside the sector.insidetextorientation- Controls the orientation of the text inside chart sectors. When set to *auto*, text may be oriented in any direction in order to be as big as possible in the middle of a sector. The *horizontal* option orients text to be parallel with the bottom of the chart, and may make text smaller in order to achieve that goal. The *radial* option orients text along the radius of the sector. The *tangential* option orients text perpendicular to the radius of the sector.labels- Sets the labels of each of the sectors.labelssrc- Sets the source reference on Chart Studio Cloud for `labels`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.level- Sets the level from which this trace hierarchy is rendered. Set `level` to `''` to start from the root node in the hierarchy. Must be an "id" if `ids` is filled in, otherwise plotly attempts to find a matching item in `labels`.maxdepth- Sets the number of rendered sectors from any given `level`. Set `maxdepth` to *-1* to render all the levels in the hierarchy.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.outsidetextfont- Sets the font used for `textinfo` lying outside the sector. This option refers to the root of the hierarchy presented at the center of a sunburst graph. Please note that if a hierarchy has multiple root nodes, this option won't have any effect and `insidetextfont` would be used.parents- Sets the parent sectors for each of the sectors. Empty string items '' are understood to reference the root node in the hierarchy. If `ids` is filled, `parents` items are understood to be "ids" themselves. When `ids` is not set, plotly attempts to find matching items in `labels`, but beware they must be unique.parentssrc- Sets the source reference on Chart Studio Cloud for `parents`.rotation- Rotates the whole diagram counterclockwise by some angle. By default the first slice starts at 3 o'clock.sort- Determines whether or not the sectors are reordered from largest to smallest.text- Sets text elements associated with each sector. If trace `textinfo` contains a *text* flag, these elements will be seen on the chart. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the font used for `textinfo`.textinfo- Determines which trace information appear on the graph.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry`, `percentParent`, `label` and `value`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.values- Sets the values associated with each of the sectors. Use with `branchvalues` to determine how the values are summed.valuessrc- Sets the source reference on Chart Studio Cloud for `values`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Surface([_deprecated=], [autocolorscale=], [cauto=], [cmax=], [cmid=], [cmin=], [coloraxis=], [colorbar=], [colorscale=], [connectgaps=], [contours=], [customdata=], [customdatasrc=], [hidesurface=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [meta=], [metasrc=], [name=], [opacity=], [opacityscale=], [reversescale=], [scene=], [showlegend=], [showscale=], [stream=], [surfacecolor=], [surfacecolorsrc=], [text=], [textsrc=], [uid=], [uirevision=], [visible=], [x=], [xcalendar=], [xhoverformat=], [xsrc=], [y=], [ycalendar=], [yhoverformat=], [ysrc=], [z=], [zcalendar=], [zhoverformat=], [zsrc=]) → Surface
Create a new ‘Surface’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here z or surfacecolor) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as z or surfacecolor and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as z or surfacecolor. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as z or surfacecolor and if set, `cmax` must be set as well.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.connectgaps- Determines whether or not gaps (i.e. {nan} or missing values) in the `z` data are filled in.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hidesurface- Determines whether or not a surface is drawn. For example, set `hidesurface` to *false* `contours.x.show` to *true* and `contours.y.show` to *true* to draw a wire frame plot.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.opacityscale- Sets the opacityscale. The opacityscale must be an array containing arrays mapping a normalized value to an opacity value. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 1], [0.5, 0.2], [1, 1]]` means that higher/lower values would have higher opacity values and those in the middle would be more transparent Alternatively, `opacityscale` may be a palette name string of the following list: 'min', 'max', 'extremes' and 'uniform'. The default is 'uniform'.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.surfacecolor- Sets the surface color values, used for setting a color scale independent of `z`.surfacecolorsrc- Sets the source reference on Chart Studio Cloud for `surfacecolor`.text- Sets the text elements associated with each z value. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the x coordinates.xcalendar- Sets the calendar system to use with `x` date data.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.ycalendar- Sets the calendar system to use with `y` date data.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the z coordinates.zcalendar- Sets the calendar system to use with `z` date data.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Table([cells=], [columnorder=], [columnordersrc=], [columnwidth=], [columnwidthsrc=], [customdata=], [customdatasrc=], [domain=], [header=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [ids=], [idssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [meta=], [metasrc=], [name=], [stream=], [uid=], [uirevision=], [visible=]) → Table
Create a new ‘Table’ object
columnorder- Specifies the rendered order of the data columns; for example, a value `2` at position `0` means that column index `0` in the data will be rendered as the third column, as columns have an index base of zero.columnordersrc- Sets the source reference on Chart Studio Cloud for `columnorder`.columnwidth- The width of columns expressed as a ratio. Columns fill the available width in proportion of their specified column widths.columnwidthsrc- Sets the source reference on Chart Studio Cloud for `columnwidth`.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Treemap([branchvalues=], [count=], [customdata=], [customdatasrc=], [domain=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [insidetextfont=], [labels=], [labelssrc=], [legendgrouptitle=], [legendrank=], [legendwidth=], [level=], [marker=], [maxdepth=], [meta=], [metasrc=], [name=], [opacity=], [outsidetextfont=], [parents=], [parentssrc=], [pathbar=], [root=], [sort=], [stream=], [text=], [textfont=], [textinfo=], [textposition=], [textsrc=], [texttemplate=], [texttemplatesrc=], [tiling=], [transform=], [uid=], [uirevision=], [values=], [valuessrc=], [visible=]) → Treemap
Create a new ‘Treemap’ object
branchvalues- Determines how the items in `values` are summed. When set to *total*, items in `values` are taken to be value of all its descendants. When set to *remainder*, items in `values` corresponding to the root and the branches sectors are taken to be the extra part not part of the sum of the values at their leaves.count- Determines default for `values` when it is not provided, by inferring a 1 for each of the *leaves* and/or *branches*, otherwise 0.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry` and `percentParent`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextfont- Sets the font used for `textinfo` lying inside the sector.labels- Sets the labels of each of the sectors.labelssrc- Sets the source reference on Chart Studio Cloud for `labels`.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.level- Sets the level from which this trace hierarchy is rendered. Set `level` to `''` to start from the root node in the hierarchy. Must be an "id" if `ids` is filled in, otherwise plotly attempts to find a matching item in `labels`.maxdepth- Sets the number of rendered sectors from any given `level`. Set `maxdepth` to *-1* to render all the levels in the hierarchy.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the trace.outsidetextfont- Sets the font used for `textinfo` lying outside the sector. This option refers to the root of the hierarchy presented on top left corner of a treemap graph. Please note that if a hierarchy has multiple root nodes, this option won't have any effect and `insidetextfont` would be used.parents- Sets the parent sectors for each of the sectors. Empty string items '' are understood to reference the root node in the hierarchy. If `ids` is filled, `parents` items are understood to be "ids" themselves. When `ids` is not set, plotly attempts to find matching items in `labels`, but beware they must be unique.parentssrc- Sets the source reference on Chart Studio Cloud for `parents`.sort- Determines whether or not the sectors are reordered from largest to smallest.text- Sets text elements associated with each sector. If trace `textinfo` contains a *text* flag, these elements will be seen on the chart. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textfont- Sets the font used for `textinfo`.textinfo- Determines which trace information appear on the graph.textposition- Sets the positions of the `text` elements.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `currentPath`, `root`, `entry`, `percentRoot`, `percentEntry`, `percentParent`, `label` and `value`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.values- Sets the values associated with each of the sectors. Use with `branchvalues` to determine how the values are summed.valuessrc- Sets the source reference on Chart Studio Cloud for `values`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).
plotly.graph_objs.Violin([alignmentgroup=], [bandwidth=], [box=], [customdata=], [customdatasrc=], [fillcolor=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hoveron=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [jitter=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [line=], [marker=], [meanline=], [meta=], [metasrc=], [name=], [offsetgroup=], [opacity=], [orientation=], [pointpos=], [points=], [quartilemethod=], [scalegroup=], [scalemode=], [selected=], [selectedpoints=], [showlegend=], [side=], [span=], [spanmode=], [stream=], [text=], [textsrc=], [transform=], [uid=], [uirevision=], [unselected=], [visible=], [width=], [x=], [x0=], [xaxis=], [xhoverformat=], [xsrc=], [y=], [y0=], [yaxis=], [yhoverformat=], [ysrc=]) → Violin
Create a new ‘Violin’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.bandwidth- Sets the bandwidth used to compute the kernel density estimate. By default, the bandwidth is determined by Silverman's rule of thumb.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.fillcolor- Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hoveron- Do the hover effects highlight individual violins or sample points or the kernel density estimate or any combination of them?hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.jitter- Sets the amount of jitter in the sample points drawn. If *0*, the sample points align along the distribution axis. If *1*, the sample points are drawn in a random jitter of width equal to the width of the violins.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover. For violin traces, the name will also be used for the position coordinate, if `x` and `x0` (`y` and `y0` if horizontal) are missing and the position axis is categorical. Note that the trace name is also used as a default value for attribute `scalegroup` (please see its description for details).offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the violin(s). If *v* (*h*), the distribution is visualized along the vertical (horizontal).pointpos- Sets the position of the sample points in relation to the violins. If *0*, the sample points are places over the center of the violins. Positive (negative) values correspond to positions to the right (left) for vertical violins and above (below) for horizontal violins.points- If *outliers*, only the sample points lying outside the whiskers are shown If *suspectedoutliers*, the outlier points are shown and points either less than 4*Q1-3*Q3 or greater than 4*Q3-3*Q1 are highlighted (see `outliercolor`) If *all*, all sample points are shown If *false*, only the violins are shown with no sample points. Defaults to *suspectedoutliers* when `marker.outliercolor` or `marker.line.outliercolor` is set, otherwise defaults to *outliers*.quartilemethod- Sets the method used to compute the sample's Q1 and Q3 quartiles. The *linear* method uses the 25th percentile for Q1 and 75th percentile for Q3 as computed using method #10 (listed on http://jse.amstat.org/v14n3/langford.html). The *exclusive* method uses the median to divide the ordered dataset into two halves if the sample is odd, it does not include the median in either half - Q1 is then the median of the lower half and Q3 the median of the upper half. The *inclusive* method also uses the median to divide the ordered dataset into two halves but if the sample is odd, it includes the median in both halves - Q1 is then the median of the lower half and Q3 the median of the upper half.scalegroup- If there are multiple violins that should be sized according to to some metric (see `scalemode`), link them by providing a non-empty group id here shared by every trace in the same group. If a violin's `width` is undefined, `scalegroup` will default to the trace's name. In this case, violins with the same names will be linked togetherscalemode- Sets the metric by which the width of each violin is determined. *width* means each violin has the same (max) width *count* means the violins are scaled by the number of sample points making up each violin.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.side- Determines on which side of the position value the density function making up one half of a violin is plotted. Useful when comparing two violin traces under *overlay* mode, where one trace has `side` set to *positive* and the other to *negative*.span- Sets the span in data space for which the density function will be computed. Has an effect only when `spanmode` is set to *manual*.spanmode- Sets the method by which the span in data space where the density function will be computed. *soft* means the span goes from the sample's minimum value minus two bandwidths to the sample's maximum value plus two bandwidths. *hard* means the span goes from the sample's minimum to its maximum value. For custom span settings, use mode *manual* and fill in the `span` attribute.text- Sets the text elements associated with each sample value. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.textsrc- Sets the source reference on Chart Studio Cloud for `text`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).width- Sets the width of the violin in data coordinates. If *0* (default value) the width is automatically selected based on the positions of other violin traces in the same subplot.x- Sets the x sample data or coordinates. See overview for more info.x0- Sets the x coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y sample data or coordinates. See overview for more info.y0- Sets the y coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
plotly.graph_objs.Volume([autocolorscale=], [caps=], [cauto=], [cmax=], [cmid=], [cmin=], [coloraxis=], [colorbar=], [colorscale=], [contour=], [customdata=], [customdatasrc=], [flatshading=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [isomax=], [isomin=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [lighting=], [lightposition=], [meta=], [metasrc=], [name=], [opacity=], [opacityscale=], [reversescale=], [scene=], [showlegend=], [showscale=], [slices=], [spaceframe=], [stream=], [surface=], [text=], [textsrc=], [uid=], [uirevision=], [value=], [valuehoverformat=], [valuesrc=], [visible=], [x=], [xhoverformat=], [xsrc=], [y=], [yhoverformat=], [ysrc=], [z=], [zhoverformat=], [zsrc=]) → Volume
Create a new ‘Volume’ object
autocolorscale- Determines whether the colorscale is a default palette (`autocolorscale: true`) or the palette determined by `colorscale`. In case `colorscale` is unspecified or `autocolorscale` is true, the default palette will be chosen according to whether numbers in the `color` array are all positive, all negative or mixed.cauto- Determines whether or not the color domain is computed with respect to the input data (here `value`) or the bounds set in `cmin` and `cmax` Defaults to `false` when `cmin` and `cmax` are set by the user.cmax- Sets the upper bound of the color domain. Value should have the same units as `value` and if set, `cmin` must be set as well.cmid- Sets the mid-point of the color domain by scaling `cmin` and/or `cmax` to be equidistant to this point. Value should have the same units as `value`. Has no effect when `cauto` is `false`.cmin- Sets the lower bound of the color domain. Value should have the same units as `value` and if set, `cmax` must be set as well.coloraxis- Sets a reference to a shared color axis. References to these shared color axes are *coloraxis*, *coloraxis2*, *coloraxis3*, etc. Settings for these shared color axes are set in the layout, under `layout.coloraxis`, `layout.coloraxis2`, etc. Note that multiple color scales can be linked to the same color axis.colorscale- Sets the colorscale. The colorscale must be an array containing arrays mapping a normalized value to an rgb, rgba, hex, hsl, hsv, or named color string. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 'rgb(0,0,255)'], [1, 'rgb(255,0,0)']]`. To control the bounds of the colorscale in color space, use `cmin` and `cmax`. Alternatively, `colorscale` may be a palette name string of the following list: Blackbody,Bluered,Blues,Cividis,Earth,Electric,Greens,Greys,Hot,Jet,Picnic,Portland,Rainbow,RdBu,Reds,Viridis,YlGnBu,YlOrRd.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.flatshading- Determines whether or not normal smoothing is applied to the meshes, creating meshes with an angular, low-poly look via flat reflections.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Same as `text`.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.isomax- Sets the maximum boundary for iso-surface plot.isomin- Sets the minimum boundary for iso-surface plot.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.opacity- Sets the opacity of the surface. Please note that in the case of using high `opacity` values for example a value greater than or equal to 0.5 on two surfaces (and 0.25 with four surfaces), an overlay of multiple transparent surfaces may not perfectly be sorted in depth by the webgl API. This behavior may be improved in the near future and is subject to change.opacityscale- Sets the opacityscale. The opacityscale must be an array containing arrays mapping a normalized value to an opacity value. At minimum, a mapping for the lowest (0) and highest (1) values are required. For example, `[[0, 1], [0.5, 0.2], [1, 1]]` means that higher/lower values would have higher opacity values and those in the middle would be more transparent Alternatively, `opacityscale` may be a palette name string of the following list: 'min', 'max', 'extremes' and 'uniform'. The default is 'uniform'.reversescale- Reverses the color mapping if true. If true, `cmin` will correspond to the last color in the array and `cmax` will correspond to the first color.scene- Sets a reference between this trace's 3D coordinate system and a 3D scene. If *scene* (the default value), the (x,y,z) coordinates refer to `layout.scene`. If *scene2*, the (x,y,z) coordinates refer to `layout.scene2`, and so on.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.showscale- Determines whether or not a colorbar is displayed for this trace.text- Sets the text elements associated with the vertices. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textsrc- Sets the source reference on Chart Studio Cloud for `text`.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.value- Sets the 4th dimension (value) of the vertices.valuehoverformat- Sets the hover text formatting rulefor `value` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format.By default the values are formatted using generic number format.valuesrc- Sets the source reference on Chart Studio Cloud for `value`.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).x- Sets the X coordinates of the vertices on X axis.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the Y coordinates of the vertices on Y axis.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.ysrc- Sets the source reference on Chart Studio Cloud for `y`.z- Sets the Z coordinates of the vertices on Z axis.zhoverformat- Sets the hover text formatting rulefor `z` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `zaxis.hoverformat`.zsrc- Sets the source reference on Chart Studio Cloud for `z`.
plotly.graph_objs.Waterfall([alignmentgroup=], [base=], [cliponaxis=], [connector=], [constraintext=], [customdata=], [customdatasrc=], [decreasing=], [dx=], [dy=], [hoverinfo=], [hoverinfosrc=], [hoverlabel=], [hovertemplate=], [hovertemplatesrc=], [hovertext=], [hovertextsrc=], [ids=], [idssrc=], [increasing=], [insidetextanchor=], [insidetextfont=], [legendgroup=], [legendgrouptitle=], [legendrank=], [legendwidth=], [measure=], [measuresrc=], [meta=], [metasrc=], [name=], [offset=], [offsetgroup=], [offsetsrc=], [opacity=], [orientation=], [outsidetextfont=], [selectedpoints=], [showlegend=], [stream=], [text=], [textangle=], [textfont=], [textinfo=], [textposition=], [textpositionsrc=], [textsrc=], [texttemplate=], [texttemplatesrc=], [totals=], [transform=], [uid=], [uirevision=], [visible=], [width=], [widthsrc=], [x=], [x0=], [xaxis=], [xhoverformat=], [xperiod=], [xperiod0=], [xperiodalignment=], [xsrc=], [y=], [y0=], [yaxis=], [yhoverformat=], [yperiod=], [yperiod0=], [yperiodalignment=], [ysrc=]) → Waterfall
Create a new ‘Waterfall’ object
alignmentgroup- Set several traces linked to the same position axis or matching axes to the same alignmentgroup. This controls whether bars compute their positional range dependently or independently.base- Sets where the bar base is drawn (in position axis units).cliponaxis- Determines whether the text nodes are clipped about the subplot axes. To show the text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*.constraintext- Constrain the size of text inside or outside a bar to be no larger than the bar itself.customdata- Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, *scatter* traces also appends customdata items in the markers DOM elementscustomdatasrc- Sets the source reference on Chart Studio Cloud for `customdata`.dx- Sets the x coordinate step. See `x0` for more info.dy- Sets the y coordinate step. See `y0` for more info.hoverinfo- Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired.hoverinfosrc- Sets the source reference on Chart Studio Cloud for `hoverinfo`.hovertemplate- Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, *xother* will be added to those with different x positions from the first point. An underscore before or after *(x|y)other* will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `initial`, `delta` and `final`. Anything contained in tag `<extra>` is displayed in the secondary box, for example "<extra>{fullData.name}</extra>". To hide the secondary box completely, use an empty tag `<extra></extra>`.hovertemplatesrc- Sets the source reference on Chart Studio Cloud for `hovertemplate`.hovertext- Sets hover text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. To be seen, trace `hoverinfo` must contain a *text* flag.hovertextsrc- Sets the source reference on Chart Studio Cloud for `hovertext`.ids- Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.idssrc- Sets the source reference on Chart Studio Cloud for `ids`.insidetextanchor- Determines if texts are kept at center or start/end points in `textposition` *inside* mode.insidetextfont- Sets the font used for `text` lying inside the bar.legendgroup- Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items.legendrank- Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with `*reversed* `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.legendwidth- Sets the width (in px or fraction) of the legend for this trace.measure- An array containing types of values. By default the values are considered as 'relative'. However; it is possible to use 'total' to compute the sums. Also 'absolute' could be applied to reset the computed total or to declare an initial value where needed.measuresrc- Sets the source reference on Chart Studio Cloud for `measure`.meta- Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index.metasrc- Sets the source reference on Chart Studio Cloud for `meta`.name- Sets the trace name. The trace name appear as the legend item and on hover.offset- Shifts the position where the bar is drawn (in position axis units). In *group* barmode, traces that set *offset* will be excluded and drawn in *overlay* mode instead.offsetgroup- Set several traces linked to the same position axis or matching axes to the same offsetgroup where bars of the same position coordinate will line up.offsetsrc- Sets the source reference on Chart Studio Cloud for `offset`.opacity- Sets the opacity of the trace.orientation- Sets the orientation of the bars. With *v* (*h*), the value of the each bar spans along the vertical (horizontal).outsidetextfont- Sets the font used for `text` lying outside the bar.selectedpoints- Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect.showlegend- Determines whether or not an item corresponding to this trace is shown in the legend.text- Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels.textangle- Sets the angle of the tick labels with respect to the bar. For example, a `tickangle` of -90 draws the tick labels vertically. With *auto* the texts may automatically be rotated to fit with the maximum size in bars.textfont- Sets the font used for `text`.textinfo- Determines which trace information appear on the graph. In the case of having multiple waterfalls, totals are computed separately (per trace).textposition- Specifies the location of the `text`. *inside* positions `text` inside, next to the bar end (rotated and scaled if needed). *outside* positions `text` outside, next to the bar end (scaled if needed), unless there is another bar stacked on this one, then the text gets pushed inside. *auto* tries to position `text` inside the bar, but if the bar is too small and no bar is stacked on this one the text is moved outside. If *none*, no text appears.textpositionsrc- Sets the source reference on Chart Studio Cloud for `textposition`.textsrc- Sets the source reference on Chart Studio Cloud for `text`.texttemplate- Template string used for rendering the information text that appear on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. variables `initial`, `delta`, `final` and `label`.texttemplatesrc- Sets the source reference on Chart Studio Cloud for `texttemplate`.transform- WARNING: All transforms are deprecated and may be removed from the API in next major version. An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.uid- Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions.uirevision- Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves.visible- Determines whether or not this trace is visible. If *legendonly*, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).width- Sets the bar width (in position axis units).widthsrc- Sets the source reference on Chart Studio Cloud for `width`.x- Sets the x coordinates.x0- Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.xaxis- Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.xhoverformat- Sets the hover text formatting rulefor `x` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `xaxis.hoverformat`.xperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the x axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.xperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the x0 axis. When `x0period` is round number of weeks, the `x0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.xperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the x axis.xsrc- Sets the source reference on Chart Studio Cloud for `x`.y- Sets the y coordinates.y0- Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.yaxis- Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.yhoverformat- Sets the hover text formatting rulefor `y` using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3's date formatter: *%h* for half of the year as a decimal number as well as *%{n}f* for fractional seconds with n digits. For example, *2016-10-13 09:15:23.456* with tickformat *%H~%M~%S.%2f* would display *09~15~23.46*By default the values are formatted using `yaxis.hoverformat`.yperiod- Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *M<n>* on the y axis. Special values in the form of *M<n>* could be used to declare the number of months. In this case `n` must be a positive integer.yperiod0- Only relevant when the axis `type` is *date*. Sets the base for period positioning in milliseconds or date string on the y0 axis. When `y0period` is round number of weeks, the `y0period0` by default would be on a Sunday i.e. 2000-01-02, otherwise it would be at 2000-01-01.yperiodalignment- Only relevant when the axis `type` is *date*. Sets the alignment of data points on the y axis.ysrc- Sets the source reference on Chart Studio Cloud for `y`.
Globals
Do you still have questions?
Our Community Forum is full of helpful information and Anvil experts.