-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
32 additions
and
6 deletions.
There are no files selected for viewing
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
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
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
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
f4d09b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@b-j-mills -- the original intention was to use location_ref rather than admin2_ref, since this is national-level data. We should discuss (if it's easier to keep it consistent, we can change the spec).
f4d09b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidmegginson I originally wrote it to use location_ref, but to be consistent with the population data I switched to admin2_ref. The population data exists at admin0, admin1, and admin2 and uses admin2_ref for all three admin levels. I can change it if needed! I thought it would be easier from the query side as well if they all referred to admin codes in the same way.
f4d09b8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the reply, @b-j-mills — that makes sense.
The question is whether we'll ever use this table for subnational risk, or we'll create a new table for that. If this table will always be for national risk, then I suggest going back to location_ref so that anyone looking at it in the future doesn't get confused; there won't be any extra query complexity, because the API uses the view regardless. But if we want to leave the door open for using the same table for subnational risk at some point in the future, then admin2_ref is also fine.