New feature/convert geographic level output #71
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.
Brief overview of changes
Adding some basic parsing around geographic levels in the output data.
Why are these changes being made?
The API currently returns shorthand geographic levels, which will be awkward to work with for end users. This change translates these to more human readable longhand versions.
Detailed description of changes
Created a new function
parse_geographic_level_codes()
, which performs this translation using an existing lookup table.Issue ticket number/s and link
Does a part of #5