Closed almccon closed 10 years ago
Any reason not to roll them into a topojson? Probably not.
With 88ad103c9e49859a5100ff4e2cb3b1c764315aee and e41ed34b4a9f3738bf1069275d4711dcdef4774e we now have one TopoJSON that's about 1MB. It looks a little rough to me when you zoom in. Maybe we need more detail, but that will start to balloon the filesize again.
Current level of detail in Massachusetts:
From that screenshot it looks like I need to have topojson to some pruning and cleanup, too.
Improved version is 1.6MB. https://github.com/stamen/moore/blob/master/assets/geojson/planning_areas.topojson
Looks fine to me. If file size is an issue, we can revisit this.
Wow, some of these are unnecessarily huge.