compare performance of projection in d3 vs R

[aappling-usgs]

Comment from jread in #36 that should be its own issue:

In the future, we'd want to know the cost of doing a projection in browser vs pre-processing it (w/ R or python, etc) and just having d3 load the path. If a viz needs to reproject (e.g., hopping between various views on a national map) then it likely makes sense to do it in browser (?), but if there is only one projection, I would think pre-processing would help us with load times, esp on slower machines or mobile.

So, maybe we need a clean way to do it both ways and implement the one that makes sense for the viz?

[jordansread]

👍 and perhaps connecting with Mary on how to set up this research task. I think there may be enough profiling or other tools in chrome devtools to compare two different index.html that use the two different patterns.

[aappling-usgs]

Good idea - those tools would be useful and fun to learn about.