stamen/open-redistricting

Is it OK to have exactly 1 GeoJSON file per project?

waldoj opened this issue · 1 comments

Is there any reason why defining the boundaries of a single district would require multiple GeoJSON files? Or can we safely rely on there being a single file per project?

I can identify no reason why this would be a problem. I speculate that this is one of those problems that's tough to resolve in the planning phase—it's only when the software is deployed, and edge cases start to pop up, that it turns out to be a problem. Worst-case, I think supporting multiple files is out of scope.