16 extract catalog data from the code of points #34
+9,705
−20
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.
Summary
Adds the catalog data for the app: all elements and vaults from the Code of Points, with one drawing for each. It also adds the script that made the data and docs that explain it.
What is in this PR
data/): 749 elements, 87 vaults, 22 element groups and 208 variant groups as JSON files, and 836 images.scripts/extract-cop/): a Python script that reads the Code of Points PDF and makes the files indata/.docs/EXTRACTION.mdexplains in plain words how the data was made and what we checked by handdata/andscripts/extract-cop/docs/DATA_MODEL.mdand the root README are updatedAbout the number of files
This PR has around 850 changed files. Almost all of them are the images, one small drawing per element and vault.
They are fine to push. Each image is about 7 kB, and all of them together are about 6 MB, so they take up very little storage.
How to review
You do not need to open every file. Look at these:
docs/EXTRACTION.md, to understand what was donescripts/extract-cop/extract.py, the scriptdata/elements.jsonand some images indata/images/Good to know
.gitignoreand must never be committed, because the rights belong to FIG.data/by hand. They are replaced when the script runs. Corrections go in the lists at the top ofextract.py.Closes #16