Parts of a Graph
- Doing It The Hard Way
- Doing It The D3 Way
Let’s say you have a table in Excel and want to graph it. It’s easy! Just point it at your rows and columns, set a few colors, and boom! A graph.
So now we want to make one of these in SVG to show it off on the interwebs. It’s going to be a bit more work. What do we need to make sure we get it right?
This graph has to be “to scale”. It has to have a coordinate system!
The x-axis goes from January 2014 to April 2014, and the y-axis goes from $0 to $80. However, the SVG is drawn in a box that’s about 200 by 300 pixels. Dates and pixels don’t map to one another on their own, so we have to specify a mapping somehow.
We can actually read the Excel graph because it’s clearly labeled. Those same labels with “$20” and “February” have to get to our screen somehow. They also need to be formatted correctly for the data type.
Our graph is showing our data! Somehow, the 4 rows in our source table need to turn into 4 points on a line. On top of that, the points in the line need to fit into the coordinate system we’ve defined.
We can kind of intuit this, but it’s critical to working with D3. We have data coming in, and we transform it to something visual.
Doing It The Hard Way
Let’s make a graph the hard way! As we’ve seen earlier, the SVG
<path> tag is
kind of complex, so we’ll swap out a line graph for a scatterplot.
We’ll need to manually write out each point. Transform attributes are inherited
by child elements, so we can use
<g> tags to move entire groups, such as the
axes, or even offset the entire graph by a margin.
Man! All that work for such a simple graph? SVG is a lot of work!
Doing It The D3 Way
Good news! D3 has pieces to help with each of the parts of a graph we listed above! However, D3 does this in the spirit of “automating the hard bits you already understand”, rather than making it all happen.
There are a few operations that come up all the time, such as finding the minimum and maximum values of a data set (even both at the same time, the “extent”).
In D3 code, it’s common to pass callbacks that are used on all elements of a
group. These callbacks are almost always called back with two arguments: the
element and its index. It’s common to name these parameters
D3 has objects called scales that help map values across coordinate systems. There are different kinds of scales (linear, logarithmic, linear for time). Scales are configured with a domain and a range, they map from the data to the approprate part of the screen (screen space).
Here is how we set up the y-scale for the above money example:
Or if we wanted to take advantage of the helper methods above:
The domain is in the data space, so its units are your source units. The range is in screen space (pixels).
This scale object is also a function! Calling the scale as a function is how we translate values from one coordinate to another.
We can even do the same things with dates!
Scales are not just for linear transforms (continuous or quantitative scales), they can also be used for arbitrary transforms (discrete or ordinal scales). We’ll come across more scales later.
In our example, up top, we have these nice labels and tick marks. This is something D3 can do for us. We can build an axis, and apply it to a scale. We say, “hey, I want to build an axis that”.
D3’s axes are really powerful! Notice how we built it using Date objects, and by default, it labeled the tick marks appopriately!
The next thing to do is take our data and transform it into something visible. This is data binding, and it’s a big topic, so it gets its own section.