Brian Jacobs

Thanks for this, I wasn't aware of the change. Feel free to close.

+1 to this as well. Maybe related, custom markup so I may style within a title or label e.g.: "Label with **bold** and _italics_ words"

Yeah that makes sense as a responsible way to apply an override for a particular export. But a few times I've run into cases where less css-savvy folks are making...

Within a local project looks like if i run `npm link` instead of `npm install -g` volta registers the local bin as expected, and appears to provide the same behavior....

Thanks. `npm link` looks identical for my purposes, a fine workaround. Didn't have any luck finding an explanation on the difference between that and `npm install -g` (no args) however....

+1 for this. A table to understand what proj4/wkt parameters map to d3 projection function arguments would be max helpful.

I still struggle with knowing what proj4 parameters map to D3 projection inputs. It's frustrating because parameters from Proj4 or WKT is all I have to lean on coming over...

The code on this page is a big clue for me. It outputs proj4 strings from chosen projections/parameters and renders it in a d3 map http://projectionwizard.org/

Gotcha, thanks. Looking back at the metadata, I never had the final dataset, so nothing to do with re-fetching the data. But glad I could surface the bug of sorts....