Rose chart API reference
- Example
- The data_seq property
- Properties
- Methods
- Stacked Rose charts
- Non-equi-angular Rose charts
- The coordinates properties
- Events
- Effects
Example
<script> data = [10,5,8,3,9,4,6,10,5,3,6,8,4,9]; labels = ['John','Richard','Paul','Pete','Lou','Olga','Neil','Ken','Luis','John','Gary','Paul','Fay','Will']; new RGraph.Rose({ id: 'cvs', data: data, options: { colors: ['red'], backgroundGridRadialsCount: 0, labels: labels, tooltips: '%{key}', tooltipsFormattedUnitsPost: 'kg', tooltipsFormattedKeyLabels: labels, margin: 5, tooltipsCss: { fontSize: '20pt', boxShadow: '', textAlign: 'left' }, textSize: 16 } }).draw(); </script>
The data_seq property
If your data is a multi-dimensional array (ie on a stacked
Rose chart
) then one member
variable may be of interest to you -
the obj.data_seq
variable. This is a flattened view of the array of data that you pass to
the Rose chart
that may be useful in some circumstances. One of the demos shows this variable being
used to get the value of the relevant piece of data.
This variable isn't really necessary for
non-equi-angular
or regular non-stacked Rose charts
.
Properties
You can use these properties to control how the chart appears. You can set them by including them in the options section of the configuration as shown above.
- Chart configuration properties
- Background properties
- Axes properties
- Margin properties
- Color properties
- Shadow properties
- Labels and text properties
- Title properties
- Scale properties
- Key properties
- Interactive features properties
- Miscellaneous properties
Chart configuration properties
Rose chart
using this instead of the margins. As well as a number, that gives the exact coordinate of the center position of the chart, this can also be a string
like this: centerx: '+25'
or this: centerx: '-40'
which is then used to adjust the calculated coordinate.Rose chart
using this instead of the margins. As well as a number, that gives the exact coordinate of the center position of the chart, this can also be a string
like this: centery: '+25'
or this: centery: '-40'
which is then used to adjust the calculated coordinate.Rose chart
using this instead of the margins. As well as a number, that gives the exact size of the chart, this can also be a string
like this: radius: '+25'
or this: radius: '-40'
which is then used to adjust the calculated coordinate.Background properties
Axes properties
Margin properties
Color properties
rgba
, you can use color definitions such as red
along with this setting to add transparency.Shadow properties
Labels and text properties
dom
text in place of canvas
text. It makes for a much higher quality text that you can also select if desired (for copy/paste operations). It won't fit all situations and you can read more about the DOM text feature here. A good way to control borders/margins/padding etc is not to set them on the canvas
but to wrap the canvas
in a div
and set them on that like this:
<div style="margin-left: 50px; display: inline-block"> <canvas id="cvs" width="650" height="250"></canvas> </div>
visible
or hidden
and it controls whether the text is clipped to the edges of the canvas
. It defaults to be visible and means you can set small margins if you wish.dom
text responds to mouse-based events or not (it sets the pointer-events
css
property to none
).center
or edge
and determines the position of the labels.Rose chart
then this is the property to use for that.Rose chart
this the property to use for that.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.%{value_formatted}
macro.css
class to the labels which you can then use for styling purposes or to make retrieving the span
tags easier (the dom
elements). If you inspect the labels in your browser's javascript
console (you will first need to enable the textAccessiblePointerevents
property) you will be able to see the other css
classes that are assigned to the labels.Title properties
textFont
setting is used (usually Arial
).4pt
bigger than the textSize
setting."-5"
- in which case it's converted to a number and added to the calculated coordinate - allowing you to adjust the calculated coordinate."-5"
- in which case it's converted to a number and added to the calculated coordinate - allowing you to adjust the calculated coordinate.marginTop
value.Scale properties
api
compatibility across chart libraries.Key properties
The key properties are documented on the key documentation page.Interactive features properties
html
.click
or mousemove
.slide
fade
or none
.%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{value_formatted}
option.%{key}
option to use.square
or circle
css
values to the key color shape that appears in the tooltip key. Note the property name is "color" and not "colors" like previous properties. It should be an object of css
properties like this: tooltipsFormattedKeyColorsCss : { border: "1px solid #ddd"; }
ul
and ol
.tooltipsFormattedListItems: [ ['Bill','Jerry','Berty'], // First tooltip ['Gill','Carrie','Lucy'], // Second tooltip ['Pob','Nobby','Hilda'] // Third tooltip ]You can use
css
to style this list - for example:.RGraph_tooltip ul#rgraph_formatted_tooltips_list li { text-align: left; color: yellow; }
th
tags.css
values applied to the tooltips pointer (a css
border, for example) then specify an object containing those values to this property. For example: tooltipsPointerCss: { borderLeft: 'gray 2px solid', borderBottom: 'gray 2px solid' }
false
tooltips are positioned next to the mouse pointer.css
that gets applied to all of the tooltips, but don't want to use the RGraph.tooltips.style
object (which gets applied to all of the tooltips on the page for every chart) you can use this property to give some per-object css
for the tooltips. These are css
styles that get applied to all of the tooltips for the specific object only. It should look like this:tooltipsCss: { fontFamily: 'Verdana', fontSize: '20pt' }
css
class the chart uses.pie-tooltipshotspotignore.html
. You can use the transparent
color to allow the rear chart to be seen in such a case. It can be:
- A single
boolean
value (ietrue
orfalse
) to enable or disable all of the hotspots -true
means the hotspot will be ignored - A single number (the zero-indexed number corresponding to the hotspot to ignore)
- An array of numbers (the numbers are the indexes of hotspots to ignore)
- An array of
boolean
true
orfalse
values - the position of these values correspond to the index(es) of the segments to ignore (for example[false, false, true, false, false]
-true
means the corresponding hotspot will be ignored)
Miscellaneous properties
null
but you can set it to a function if you wish so that function is called to do the chart highlighting. It's passed the shape object as an argument. As of version 5.23 you can also set this to invert
as well. If you do this on a dark background you may find that you need to change the highlightFill
color setting as well.stacked
(the default) or non-equi-angular
. Just because this option is set to stacked
does not automatically mean your chart is stacked. If you don't supply the appropriate data your chart may well appear as a regular Rose chart
. Examples of appropriate data:A regular Rose chart
var rose = new RGraph.Rose({
id: 'cvs',
data: [8,5,4,8,6,7,2,3,5,8],
options: {
// variant: '3d'
}
}).draw();
A stacked Rose chart
var rose = new RGraph.Rose({
id: 'cvs',
data: [
[2,6], [2,4], [1,5], [4,3], [7,5],
[8,3], [4,5], [3,4], [2,6], [4,5]
],
options: {
variant: 'stacked'
// variant: 'stacked3d'
}
}).draw();
A non-equi-angular Rose chart
var rose = new RGraph.Rose({
id: 'cvs',
data: [
[45,23], [45,23], [5,26], [78,4], [49,12],
[49,21], [40,18], [48,12], [43,23], [45,12]
],
options: {
variant: 'non-equi-angular'
//variant: 'non-equi-angular3d'
}
}).draw();
It is important to note that with a non-equi-angular each "value" is actually an array consisting of two values, as shown. The first value represents the magnitude of the segment (ie how far the segment extends outwards), and the second value represents the size of the segment. The second value is relative to all the other second values - it is not the absolute angle used. The angle is calculated for you.
.Rose chart
when in 3D mode. Using larger depths can make the labels be drawn over the labels.[15,0,20,25]
). The values are the distance from the center that the segment is.canvas
.Methods
obj.get(name)
An accessor that you can use to retrieve the values of properties.
obj.set(name, value)
An accessor that you can use to set the values of properties.
obj.getShape(event)
This method makes it easy to get hold of which segment has been clicked on or hovered over. It returns an object which has the following indexes available:
object |
The chart object |
x |
This is the center X coordinate for the segment. |
y |
This is the center Y coordinate for the segment. |
radiusStart |
This is the start radius of the segment. Because you can have stacked segments in a
Rose chart this is necessary.
|
radiusEnd |
This is the end radius of the segment. |
angleStart |
This is the start angle of the segment. It's measured in radians - not degrees. 1 radian = 57.29 degrees. |
angleEnd |
This is the end angle of the segment. It's measured in radians - not degrees. 1 radian = 57.29 degrees. |
dataset |
This is the group that the segment or part-segment belongs to. In a regular Rose chart ,
each segment has a distinct group number. On a stacked Rose chart , this identifies each
stack of part-segments. In a non-equi-angular chart, this is always zero.
|
index |
The zero-indexed index of the segment on the chart. In a stacked Rose chart this is
the index in a particular stack, whereas in a regular Rose chart this is the index
of the segment in the whole dataset. Likewise for a non-equi-angular
dataset.
|
sequentialIndex |
This is the zero-indexed sequential index of the segment on
the chart. No matter what the type of Rose chart that you're showing this just starts at zero
and counts up for each segment.
|
tooltip |
If a tooltip is associated with this segment this will be it. id:
strings are expanded for you (where the tooltip text is retrieved from the html
tag with the matching ID).
|
<script> rose.canvas.onclick = function (e) { RGraph.redraw(); var canvas = e.target, obj = canvas.__object__, shape = obj.getShape(e); if (shape) { var x = shape.x, y = shape.y, radiusStart = shape.radiusStart, radiusEnd = shape.radiusEnd, angleStart = shape.angleStart, angleEnd = shape.angleEnd; // Path the outer edge of the segment obj.path( 'b lw 3 a % % % % % false', x, y, radiusEnd, angleStart, angleEnd ); // Path the inner edge of the segment - but going anti-clockwise! obj.path( 'a % % % % % true c s black f red', x, y, radiusStart, angleEnd, angleStart ); } } </script>
obj.getRadius(value)
This method can be used to get the relevant radius for a given scale value.
obj.on(event, function)
This method can be used to set an event listener on an object. It
operates similarly to the jquery
on
function.
The first argument is the event that you wish to attach to and the
second is the handler function. For example:
.on('draw', function (obj)
{
// Put your event code here
});
The function is useful if you use method chaining when creating your charts:
var obj = new RGraph.Rose({ id: 'cvs', data: [4,8,6,3,5,8,4,6], options: { } }).on('draw', function (obj) { // Put your draw event code here }).on('click', function (e, shape) { // Put your click event code here }).draw();
obj.exec(function)
The exec function is documented here.
obj.responsive(configuration)
The responsive
function helps your charts
respond to different browser window sizes and screen
resolutions. For example, for smaller screens, you
might want to have angled labels or show shorter
versions of them completely.
Update: There is now the responsive configuration option available to you and this is now the preferred method of configuration.
The responsive function and configuration option are documented on their own page here.
Stacked Rose charts
Rose charts
can now be stacked, much like stacked Bar charts
. For
examples of them, see the Rose chart
example pages in
the download archive. The data
for a stacked Rose chart
should be supplied in the same format as
a stacked Bar chart
:
<script> new RGraph.Rose({ id: 'cvs', data: [[4,6,2],[8,4,7],[4,3,6],[1,5,6]], options: { } }).draw(); </script>
Non-equi-angular Rose charts
Rose charts
can be displayed in a non-equi-angular
mode. For an
example see this
Rose chart
demo page in the download archive:
rose-non-equi-angular.html.
Instead of a plain array of values (as with a regular
Rose chart
), each data point should itself be a two element array
consisting of the magnitude value and also a relative
circular size. This second value is not the size of the angle
- this is calculated. For example:
<script> new RGraph.Rose({ id: 'cvs', data: [[47,6],[48,2],[40,4],[43,5],[45,6]], options: { variant: 'non-equi-angular' } }).draw(); </script>
The coordinates properties
The details of the segments on the Rose chart
are
available to you via the obj.angles
and obj.angles2
arrays
. These
organise the angles in a similar way to how the
Bar chart
makes the obj.coords
and obj.coords2
arrays
available to you.
-
obj.angles
This holds the information about the segments that make up the Rose chart. The properties that each entry holds are:- start angle (measured in radians)
- end angle (measured in radians)
- start radius
- radius
- center
x
coordinate - center
y
coordinate - stroke color
- fill color
-
obj.angles2
This is similar to the abovearray
but is indexed differently - first by group and then by iindex. Each entry holds the following information:- start angle (measured in radians)
- end angle (measured in radians)
- start radius
- radius
- center
x
coordinate - center
y
coordinate - stroke color
- fill color
-
obj.coordsText
This holds the coordinates of all of the text that has been added to the chart. Even if the text is blank (ie no text) then the coordinates will be added to this variable.
Events
RGraph supports custom events that allow you to easily add interactivity to your charts if required. The following events are available:
annotatebegin
This event fires at the start of annotating - like the standardmousedown
event.annotate
This event fires (repeatedly) during annotating - like the standardmousemove
event.annotateend
This event fires at the end of annotating - like the standardmouseup
event.annotateclear
This event fires at the end of theRGraph.clearAnnotations
function.beforeclear
This event fires at the start of theRGraph.clear
function.clear
This event fires at the end of theRGraph.clear
function.click
This is similar to the standardcanvas
click
event but this only fires when you click on a bar - not the wholecanvas
.beforecontextmenu
This event fires when you have the contextmenu enabled and it is about to appear.contextmenu
This event fires when you have the contextmenu enabled and it has been displayed.beforedraw
This event fires at the start of thedraw
method before anything has been done.firstdraw
This event fires at the end of thedraw
function - but only the first time that thedraw
function is called.draw
This event fires at the end of thedraw
function.beforeinteractivekey
When you're using the interactive key this event fires just before the key and chart are highlighted.afterinteractivekey
When you're using the interactive key this event fires just after the key and chart are highlighted.keyclick
This event fires when you click on the key - you don't have to be using the interactive key however.mousemove
This event is similar to the standardmousemove
event but only fires when you move the mouse over a bar on the chart.mouseover
This event is similar to the standardmouseover
event but only fires when you move the mouse over a bar on the chart.mouseout
This event is similar to the standardmouseout
event but only fires when you move the mouse away from a bar on the chart that you've previously hovered over.beforetooltip
This event fires at the start of the tooltip showing process.tooltip
This event fires after a tooltip has been shown.
new RGraph.Rose({ id: 'cvs', data: [4,8,6,3,5,8,9], options: { } }).on('draw', function (obj) { console.log('The draw event has fired'); }).draw();
Effects
These effects are available and can be used instead of thedraw
function. There are also generic effects available which
you can see here: Generic effects and transitions
- The
grow
effect (effects-rose-grow.html in the download archive) - The
roundRobin
effect (effects-rose-roundrobin.html in the download archive) - The
implode
effect (effects-rose-implode.html in the download archive) - The
explode
effect (effects-rose-explode.html in the download archive) - The
wave
effect (effects-rose-wave.html in the download archive)
<script> // Optional callback function that's called when the effect is complete function myCallback (obj) { // ... } new RGraph.Rose({ id: 'cvs', data: [8,6,3,5,2,4,8], options: { marginLeft: 35 } }).grow({frames: 60}, myCallback) // .roundRobin({frames: 60}, myCallback) // .implode({frames: 60}, myCallback) // .explode({frames: 60}, myCallback) </script>