# d3-voronoi-map This D3 plugin produces a _Voronoï map_ (i.e. one-level treemap). Given a convex polygon and weighted data, it tesselates/partitions the polygon in several inner cells, such that the area of a cell represents the weight of the underlying datum. Because a picture is worth a thousand words: ![square](./img/square.png) ![hexagon](./img/hexagon.png) ![diamond](./img/diamond.png) ![circle](./img/circle.png) ![simulation](./img/simulation.gif) Available for **d3 v4**, **d3 v5** and **d3 v6**. If you're interested on multi-level treemap, which handle nested/hierarchical data, take a look at the [d3-voronoi-treemap](https://github.com/Kcnarf/d3-voronoi-treemap) plugin. ## Context D3 already provides a [d3-treemap](https://github.com/d3/d3-hierarchy/blob/master/README.md#treemap) module which produces a rectangular treemap. Such treemaps could be distorted to fit shapes that are not rectangles (cf. [Distorded Treemap - d3-shaped treemap](http://bl.ocks.org/Kcnarf/976b2e854965eea17a7754517043b91f)). This plugin allows to compute a map with a unique look-and-feel, where inner areas are not strictly aligned each others, and where the outer shape can be any hole-free convex polygons (square, rectangle, pentagon, hexagon, ... any regular convex polygon, and also any non regular hole-free convex polygon). The computation of the Voronoï map is based on a iteration/looping process. Hence, obtaining the final partition requires _some iterations_/_some times_, depending on the number and type of data/weights, the desired representativeness of cell areas. As the [d3-force](https://github.com/d3/d3-force) layout does, this module can be used in two ways : - live Voronoï map: displays the evolution of the self-organizing Voronoï map; each iteration is displayed, with some delay between iterations so that the animation is appealing to human eyes; - static Voronoï map: displays only the final most representative Voronoï map, which is faster than the _live_ use case; intermediate iterations are silently computed, one after each other, without any delay. The rest of this README gives some implementatiton details and example on these two use cases. ## Examples - Real life use cases - [Democratic Primaries: Preferential Poll Results](https://swayable.com/insights/primaries2019) by Nadieh Bremer in Swayable, with animated Voronoï maps (more details at https://www.visualcinnamon.com/portfolio/swayable-preferential-polling) - [The Battleground States Biden and Trump Need to Win 270](https://www.nytimes.com/interactive/2020/us/elections/election-states-biden-trump.html) by in The New York Times, with interactive and playful Voronoï maps - [Land of colors](https://public.tableau.com/profile/guillevin#!/vizhome/LandOfColors/Landofcolors) by Tristan Guillevin in Tableau, with small multiples Voronoï maps - Examples with available code - [The Individual Costs of Being Obese in the U.S. (2010)](https://bl.ocks.org/kcnarf/89d9d2d575f5c4ad41235cad6b202742), a remake of [HowMuch.net's post](https://howmuch.net/articles/obesity-costs-visualized) - a [simple example](https://bl.ocks.org/Kcnarf/95fbcdb4e58a4e048867667c23071a28) explains how to switch from a live arrangement to a static arrangement - a [simple example](https://bl.ocks.org/Kcnarf/81f4ce6a76abe132427a29b1519caee8) and [Global Population by Region by 1950 to 2100 - a remake](https://bl.ocks.org/Kcnarf/6195b6ec020c180ad50a14b739510ddc) explain how to update and animate an existing arrangement ## Installing If you use NPM, `npm install d3-voronoi-map` and import it with ```js import { voronoiMapSimulation } from 'd3-voronoi-map'; ``` Otherwise, load `https://rawcdn.githack.com/Kcnarf/d3-voronoi-map/v2.1.1/build/d3-voronoi-map.js` (or its `d3-voronoi-map.min.js` version) to make it available in AMD, CommonJS, or vanilla environments. In vanilla, you must load the [d3-weighted-voronoi](https://github.com/Kcnarf/d3-weighted-voronoi) plugin prior to this one, and a d3 global is exported: ```html ``` If you're interested in the latest developments, you can use the master build, available throught: ```html ``` ## TL;DR; In your javascript, if you want to display a live Voronoï map (i.e. displays the evolution of the self-organizing Voronoï map) : ```javascript var simulation = d3.voronoiMapSimulation(data) .weight(function(d){ return weightScale(d); } // set the weight accessor .clip([[0,0], [0,height], [width, height], [width,0]]) // set the clipping polygon .on ("tick", ticked); // function 'ticked' is called after each iteration function ticked() { var state = simulation.state(), // retrieve the simulation's state, i.e. {ended, polygons, iterationCount, convergenceRatio} polygons = state.polygons, // retrieve polygons, i.e. cells of the current iteration drawnCells; drawnCells = d3.selectAll('path').data(polygons); // d3's join drawnCells .enter().append('path') // create cells at first render .merge(drawnCells); // assigns appropriate shapes and colors .attr('d', function(d) { return cellLiner(d) + 'z'; }) .style('fill', function(d) { return fillScale(d.site.originalObject); }); } ``` Or, if you want to display only the static Voronoï map (i.e. display the final most representative arrangement): ```javascript var simulation = d3.voronoiMapSimulation(data) .weight(function(d){ return weightScale(d); } // set the weight accessor .clip([[0,0], [0,height], [width, height], [width,0]]) // set the clipping polygon .stop(); // immediately stops the simulation var state = simulation.state(); // retrieve the simulation's state, i.e. {ended, polygons, iterationCount, convergenceRatio} while (!state.ended) { // manually launch each iteration until the simulation ends simulation.tick(); state = simulation.state(); } var polygons = state.polygons; // retrieve polygons, i.e. cells of the final Voronoï map d3.selectAll('path').data(polygons); // d3's join .enter() // create cells with appropriate shapes and colors .append('path') .attr('d', function(d) { return cellLiner(d) + 'z'; }) .style('fill', function(d) { return fillScale(d.site.originalObject); }); ``` ## Reference - based on [Computing Voronoï Treemaps - Faster, Simpler, and Resolution-independent ](https://www.uni-konstanz.de/mmsp/pubsys/publishedFiles/NoBr12a.pdf) - [https://github.com/ArlindNocaj/power-voronoi-diagram](https://github.com/ArlindNocaj/power-voronoi-diagram) for a Java implementation ## API # d3.voronoiMapSimulation(data) Creates a new simulation with the specified array of data, and the default accessors and configuration values ([_weight_](#simulation_weight), [_clip_](#simulation_clip), [_convergenceRatio_](#simulation_convergenceRatio), [_maxIterationCount_](#simulation_maxIterationCount), [_minWeightRatio_](#simulation_minWeightRatio), [_prng_](#simulation_prng), [_initialPosition_](#simulation_initialPosition), and [_initialWeight_](#simulation_initialWeight)). The simulation starts automatically. For a [live](#live) Voronoï map, use [simulation.on](#simulation_on) to listen for _tick_ events as the simulation runs, and _end_ event when the simulation finishes. See also [TL;DR; live Voronoï map](#tldr_live). For a [static](#static) Voronoï map, call [simulation.stop](#simulation_stop), and then call [simulation.tick](#simulation_tick) as desired. See also [TL;DR; static Voronoï map](#tldr_static). # simulation.state() Returns a _hash_ of the current state of the simulation. _hash.polygons_ is a sparse array of polygons clipped to the [_clip_](#simulation_clip)-ping polygon, one for each cell (each unique input point) in the diagram. Each polygon is represented as an array of points \[_x_, _y_\] where _x_ and _y_ are the point coordinates, a _site_ field that refers to its site (ie. with x, y and weight retrieved from the original data), and a _site.originalObject_ field that refers to the corresponding element in _data_ (specified in [d3.voronoiMapSimulation(data)](#voronoiMapSimulation)). Polygons are open: they do not contain a closing point that duplicates the first point; a triangle, for example, is an array of three points. Polygons are also counterclockwise (assuming the origin ⟨0,0⟩ is in the top-left corner). Furthermore : - the positive integer _hash.iterationCount_ is the current iteration count; - the floating number _hash.convergenceRatio_ is the current convergence ratio (ie. cell area errors / area of the [_clip_](#simulation_clip)-ping polygon); - the boolean _hash.ended_ indicates if the current iteration is the final one, or if the simulation requires more iterations to complete. # simulation.weight([weight]) If _weight_-accessor is specified, sets the _weight_ accessor. If _weight_ is not specified, returns the current _weight_ accessor, which defaults to: ```js function weight(d) { return d.weight; } ``` # simulation.clip([clip]) If _clip_ is specified, sets the clipping polygon, compute the adequate [_extent_](#simulation_extent) and [_size_](#simulation_size), and returns this layout. _clip_ defines a hole-free convex polygon, and is specified as an array of 2D points \[x, y\], which must be _(i)_ open (no duplication of the first D2 point) and _(ii)_ counterclockwise (assuming the origin ⟨0,0⟩ is in the top-left corner). If _clip_ is not specified, returns the current clipping polygon, which defaults to: ```js [ [0, 0], [0, 1], [1, 1], [1, 0], ]; ``` # simulation.extent([extent]) If _extent_ is specified, it is a convenient way to define the clipping polygon as a rectangle. It sets the extent, computes the adequate [_clip_](#simulation_clip)ping polygon and [_size_](#simulation_size), and returns this layout. _extent_ must be a two-element array of 2D points \[x, y\], which defines the clipping polygon as a rectangle with the top-left and bottom-right corners respectively set to the first and second points (assuming the origin ⟨0,0⟩ is in the top-left corner on the screen). If _extent_ is not specified, returns the current extent, which is `[[minX, minY], [maxX, maxY]]` of current clipping polygon, and defaults to: ```js [ [0, 0], [1, 1], ]; ``` # simulation.size([size]) If _size_ is specified, it is a convenient way to define the clipping polygon as a rectangle. It sets the size, computes the adequate [_clip_](#simulation_clip)ping polygon and [_extent_](#simulation_extent), and returns this layout. _size_ must be a two-element array of numbers `[width, height]`, which defines the clipping polygon as a rectangle with the top-left corner set to `[0, 0]`and the bottom-right corner set to `[width, height]`(assuming the origin ⟨0,0⟩ is in the top-left corner on the screen). If _size_ is not specified, returns the current size, which is `[maxX-minX, maxY-minY]` of current clipping polygon, and defaults to: ```js [1, 1]; ``` # simulation.convergenceRatio([convergenceRatio]) If _convergenceRatio_ is specified, sets the convergence ratio, which stops simulation when (cell area errors / ([_clip_](#simulation_clip)-ping polygon area) <= _convergenceRatio_. If _convergenceRatio_ is not specified, returns the current _convergenceRatio_ , which defaults to: ```js var convergenceRation = 0.01; // stops computation when cell area error <= 1% clipping polygon's area ``` The smaller the _convergenceRatio_, the more representative is the final map, the longer the simulation takes time. # simulation.maxIterationCount([maxIterationCount]) If _maxIterationCount_ is specified, sets the maximum allowed number of iterations, which stops simulation when it is reached, even if the [_convergenceRatio_](#simulation_convergenceRatio) is not reached. If _maxIterationCount_ is not specified, returns the current _maxIterationCount_ , which defaults to: ```js var maxIterationCount = 50; ``` If you want to wait until simulation stops _only_ when the [_convergenceRatio_](#simulation_convergenceRatio) is reached, just set the _maxIterationCount_ to a large amount. Be warned that simulation may take a huge amount of time, due to flickering behaviours in later iterations. # simulation.minWeightRatio([minWeightRatio]) If _minWeightRatio_ is specified, sets the minimum weight ratio, which allows to compute the minimum allowed weight (_= maxWeight \* minWeightRatio_). If _minWeightRatio_ is not specified, returns the current _minWeightRatio_ , which defaults to: ```js var minWeightRatio = 0.01; // 1% of maxWeight ``` _minWeightRatio_ allows to mitigate flickerring behaviour (caused by too small weights), and enhances user interaction by not computing near-empty cells. # simulation.prng([prng]) If _prng_ is specified, sets the pseudorandom number generator which is used when randomness is required (e.g. in `d3.voronoiMapInitialPositionRandom()`, cf. [_initialPosition_](#simulatrion_initialPosition)). The given pseudorandom number generator must implement the same interface as `Math.random` and must only return values in the range [0, 1[. If _prng_ is not specified, returns the current _prng_ , which defaults to `Math.random`. _prng_ allows to handle reproducibility. Considering the same set of data, severall Voronoï map computations lead to disctinct final arrangements, due to the non-seedable `Math.random` default number generator. If _prng_ is set to a _seedable_ pseudorandom number generator which produces repeatable outputs, then several computations will produce the exact same final arrangement. This is useful if you want the same arrangement for distinct page loads/reloads. For example, using [seedrandom](https://github.com/davidbau/seedrandom): ```js ``` You can also take a look at [d3-random](https://github.com/d3/d3-random) for random number generator from other-than-uniform distributions. # simulation.initialPosition([initialPosition]) If _initialPosition_ is specified, sets the initial coordinate accessor. The accessor is a callback wich is passed the datum, its index, the array it comes from, and the current _simulation_. The accessor must provide an array of two numbers `[x, y]` inside the clipping polygon, otherwise a random initial position is used instead. If _initialPosition_ is not specified, returns the current accessor, which defaults to a random position policy which insure to randomly pick a point inside the clipping polygon. A custom accessor may look like: ```js function precomputedInitialPosition(d, i, arr, simulation) { return [d.precomputedX, d.precomputedY]; } ``` Furthermore, two predefined policies are available: - the random policy, available through `d3.voronoiMapInitialPositionRandom()`, which is the default intital position policy; it uses the specified [_prng_](#simulation_prng), and may produce repeatable arrangement if a seeded random number generator is defined; - the pie-based policy, available through `d3.voronoiMapInitialPositionPie()` which initializes positions of data along an inner circle of the clipping polygon, in an equaly distributed counterclockwise way (reverse your data to have a clockwise counterpart); the first datum is positioned at 0 radian (i.e. at right), but this can be customized through the `d3.voronoiMapInitialPositionPie().startAngle()` API; the name of this policy comes from the very first iteration which looks like a pie; You can take a look at these policies to define your own complex initial position policies/accessors. # voronoiMap.initialWeight([initialWeight]) If _initialWeight_ is specified, sets the initial weight accessor. The accessor is a callback wich is passed the datum, its index, the array it comes from, and the current _simulation_. The accessor must provide a positive amount. If _initialWeight_ is not specified, returns the current accessor, which defaults to initialize all sites with the same amount (which depends on the clipping polygon and the number of data): A custom accessor may look like: ```js function precomputedInitialWeight(d, i, arr, simulation) { return d.precomputedWeight; } ``` Furthermore, the default half average area policy is available through `d3.voronoiMapInitialWeightHalfAverageArea()`. Considering a unique clipping polygon where you want animate the same set of data but with evolving weights (e.g., animate according to passing time), this API combined with the [_initialPosition_](#simulation_initialPosition) API allows you to maintain areas from one set to another: - first, compute the Voronoï map of a first set of data - then, compute the Voronoï map of another set of data, by initializing sites to the final values (positions and weights) of first Voronoï map See [Update and Animate a Voronooï map](https://bl.ocks.org/Kcnarf/81f4ce6a76abe132427a29b1519caee8) or [Global Population by Region from 1950 to 2100 - a remake](https://bl.ocks.org/Kcnarf/6195b6ec020c180ad50a14b739510ddc) for live examples. # simulation.stop() Stops the simulation’s internal timer, if it is running, and returns the simulation. If the timer is already stopped, this method does nothing. This method is useful to display only a [static](#static) Voronoï map. In such a case, you have to stop the simulation, and run it manually till its end with [simulation.tick](#simulation_tick) (see also [TL;DR; static Voronoï map](#tldr_static)). # simulation.tick() If the simulation is not ended, computes a more representative Voronoï map by adapting the one of the previous iteration, and increments the current iteration count. If the simulation is ended, it does nothing. This method does not dispatch events; events are only dispatched by the internal timer when the simulation is started automatically upon creation or by calling [simulation.restart](#simulation_restart). This method can be used in conjunction with [simulation.stop](#simulation_stop) to compute a [static](#static) Voronoï map (see also [TL;DR; static Voronoï map](#tldr_static)). For large graphs, static layouts should be computed in a web worker to avoid freezing the user interface. # simulation.restart() Restarts the simulation’s internal timer and returns the simulation. This method can be used to resume the simulation after temporarily pausing it with [simulation.stop](#simulation_stop). # simulation.on(typenames, [listener]) If listener is specified, sets the event listener for the specified typenames and returns this simulation. If an event listener was already registered for the same type and name, the existing listener is removed before the new listener is added. If listener is null, removes the current event listeners for the specified typenames, if any. If listener is not specified, returns the first currently-assigned listener matching the specified typenames, if any. When a specified event is dispatched, each listener will be invoked with the this context as the simulation. The typenames is a string containing one or more typename separated by whitespace. Each typename is a type, optionally followed by a period (.) and a name, such as tick.foo and tick.bar; the name allows multiple listeners to be registered for the same type. The type must be one of the following: - tick - after each tick of the simulation’s internal timer. - end - after the simulation’s timer stops when alpha < alphaMin. Note that tick events are not dispatched when [simulation.tick](#simulation_tick) is called manually when only displaying a [static] Voronoï map; events are only dispatched by the internal timer, and are intended for the [live](#live) Voronoï map. See [dispatch.on](https://github.com/d3/d3-dispatch#dispatch_on) for details. ## Migrations ### From v1.x.x to v2.x.x In v1.x.x, the plugin only allows to compute a [static](#static) Voronoï map. In order to maintain this behaviour with v2.x.x, your should update your code as it is described in [TL;DR; static Voronoï map](#tldr_static). Regarding the API: - all the APIs of v1.x.x are available in v2.x.x - v2.x.x adds APIs related to the simulation (i.e. [simulation.stop](#simulation_stop), [simulation.tick](#simulation_tick), [simulation.restart](#simulation_restart), [simulation.on](#simulation_on) and [simulation.state](#simulation_state)) - `simulation.state().polygons` is the new way to retrieve cells. ## Dependencies - d3-dispatch.dispatch - d3-polygon.{polygonArea, polygonCentroid, polygonContains} - d3-timer.timer - d3-weighted-voronoi.weightedVoronoi ## Semantic Versioning d3-voronoi-map attempts to follow [semantic versioning](https://semver.org) and bump major version only when backwards incompatible changes are released.

d3-voronoi-map

Downloads in past1 Month3 Months6 Months1 Year2 Years5 YearsAll time

Stats

Sick of boring JavaScript newsletters?

Downloads in past