Florian Ledermann
Florian Ledermann
D3's scale system has proven to be insufficient for our purposes. We need a scale system that fulfills the following needs: - introspection of scale objects to find out about...
Right now, in metadata we have values like "color" that don't even match attribute names, then we have attributes directly in the metadata object, but also wrapper objects like "undefinedSymbols"...
Currently the legend supports only a single symbolization (by default the last one applied with `.symbolizeAttribute()`). Multiple legend "sections" for different symbolizers should be supported.
The code to generate SVG legends has bit-rot and has been removed, we should recreate it in the future. If you want to help, look at the [code for HTML...
Metadata should contain the URL the information was acquired from - this can be used for "traditional" layer-based sorting and filtering, for example.
Need to investigate how to best test browser & D3 based stuff. Most important for now would be some kind of integration testing to make sure the build doesn't break...
For 0.3 the mapmap.js source code should be modularized for better overview. See [D3's modularization](https://github.com/d3/d3-selection) and [rollup](https://github.com/rollup/rollup), [rollup-starter-project](https://github.com/eventualbuddha/rollup-starter-project)
Multiple maps on the same page may use the same geometry or data files, so we should cache the loaded files in the mapmap singleton to avoid multiple requests for...
Currently, choropleth maps (i.e. setting the `fill` attribute) are pretty much hardwired into `.meta()`, `.legend()` etc. - for the next major release there should be a more flexible way to...