Transforming numbers into colors is tricky. Unlike positional encodings, which our visual system automatically quantifies (this dot is twice as far from the baseline as the other), we don’t have any notion of a particular shade of red being twice as red as another. Since maps typically use position to display geometry, we’re stuck using the less effective color channel to communicate numbers (with some exceptions).

This post describes several d3 quantitative scales - linear, quantize, quantile and threshold - and walks through how they work and the trade offs involved when using them to display colors.

We start with an array of objects - `places`

- representing the filled in areas on the right choropleth. Each has a `value`

property equal to a number that we’ll encode as a color using the `colorScale`

defined in the center code snippet. The scatter plot on the left shows the distribution of values.

The code in the center uses a few libraries: `purples`

an array of 5 colorbrewer purple shades, `_`

library of helper functions, `ss`

simple-statistics, `ƒ`

a field accessor, and `d3`

itself.

colorScale = d3.scale.linear() .domain(d3.extent(places, ƒ(‘value’))) .range([purples[0], _.last(purples)])

colorScale = d3.scale.quantize() .domain(d3.extent(places, ƒ(‘value’))) .range(purples)

colorScale = d3.scale.quantile() .domain(places.map(ƒ(‘value’))) .range(purples)

breaks = ss.jenks(places.map(ƒ(‘value’)), 5) breaks[4] = breaks[4] + 1 colorScale = d3.scale.quantile() .domain(breaks.slice(1)) .range(purples)

`d3.scale.linear()`

returns a function that uses linear interpolation to transform a value in the domain into one in the range. `d3.extent`

finds the minimum and maximum numbers the value property takes on, which is then used to set the domain. The range is set to the lightest and darkest shades of purple. Internally, `d3.interpolate`

detects that the range is a color and has `colorScale`

return lighter shades of purple when passed lower numbers and darker shades when passed higher numbers. By default the colors are interpolated through an RGB color space; d3 also supports other color spaces with better perceptually properties.

Even when using a good color space, linear interpolation isn’t great for choropleths. Our perception of an object’s darkness depends on how dark its neighbors are, which makes it difficult to compare areas that aren’t adjacent. We can avoid this problem by using just a few easily discernible colors that are comparable across the graphic instead of a slightly different color for every value. Using discrete colors comes at a cost of not being able to see small differences between values, but since color conveys those differences poorly the trade off is usually worth it.

A quantize scale divides values into several discrete buckets, assigning a color to each based on which bucket it falls into. As with the linear scale, the domain is set to the minimum and maximum values. Instead of passing two colors to the range however, an array of colors is passed. The scale function then creates a bucket for each color, shown by the 5 horizontal bars on the left scatter plot.

The quantize scale divides the range of values evenly so that values in the bottom 5th – those between `minValue`

and `minValue + 1/5*(maxValue + minValue)`

– are put in the first bucket with the lightest color, while values in the the top 5th are put in the darkest bucket. More formally, values in the nth bucket will be between `minValue + n/purples.length*(maxValue - minValue)`

and `minValue + (n + 1)/purples.length*(maxValue - minValue)`

.

While the quantize scale makes intuitive sense and is simple to implement, skewed data or outliers can totally alter the color scale. Here a few very large values stretch out the scale, compressing the rest of the values into one color bucket which results in a map with just two colors. Visual differences between lower values are erased and the two remaining colors don’t intrinsically communicate anything about the proportions between the values they represent.

A quantile scale ensures that every color in the range will be used by placing values into color buckets based on their sorted order. Unlike the domains of linear and quantize scales, which only take a `minValue`

and a `maxValue`

, the quantile scale uses the entire (sorted) population of values. The size of each bucket is calculated using the ratio between the number of values and the number of colors in the domain.

Here, there are 70 values and 5 colors so each bucket has 14 values in it. The first bucket has the 14 lowest values, which are colored the lightest shade of purple; the second contains the 15th through 29th lowest values, and so on. On the scatter plot, the previously horizontal bars are now vertical as the colors of each place is determined by its rank, not value.

Because the quantile scale always puts the same number of values into each bucket, every distribution of values will be colored the same way. Here there are 5 distinct groups of values and 5 colors, but some values in different groups share a color – potentially obscuring an interesting pattern.

The Jenks natural breaks algorithm uses dynamic programing to find groupings of value so that the difference of values within a group is minimized. The breaks for our population of values are calculated and, after light manipulation, passed to a domain of a threshold scale. Each break in the domain is matched with a color in the range; values are colored based on the largest break which they are smaller than. Like the quantize scale, the horizontal rectangles show where the breaks occur.

While much of data visualization involves encoding data with marks and colors, good data visualization requires careful thinking about what to obscure and *not* show. All of the above nonlinear scales hide information about the distribution of values within a color shade to compensate for our eyes’ inability to accurately to decode color gradients. Grouping values in different ways can also mask or highlight different aspects of the data. Since there isn’t a perfect method of showing every data set, picking the right aspect of the data to not show (instead of allowing your defaults to pick for you) requires experimenting and examining the data in multiple ways.

Robert Simmons’ “Subleties of Color” articles and talk is a great introduction to difficulties of using color.

Gregor Aisch’s critique of a Guardian choropleth shows how color scale decisions (or lack thereof) can change the story a map tells (his posts on chroma.js are also excellent).

From a more academic perspective, Carlos Scheidegger has a demo showing how some of these map coloring issues fit into his algebraic vis framework.

Chapter 5, “Marks and Channels”, of Tamara Munzner’s “Visualization Analysis & Design” introduces the literature on encoding information and lays the groundwork for thinking carefully about these issues.