Add script to produce FeatureCollection files per state and type of district #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The script produces a FeatureCollection type of GeoJSON file which contains all the information in individual feature files representing individual districts. While the individual files system is a good way to organize information as an ultimate source-of-truth, the files this script produces are useful for gaining a big-picture perspective on the data. This script produces such files where applicable, is readable, and works rather quickly.
I have on my fork also a branch with the files it generates committed in case the maintainers of this repository find this to be an agreeable proposition. What do you guys think?