Conversation
aaron-kaplan
left a comment
aaron-kaplan
left a comment
There was a problem hiding this comment.
This currently doesn't work, probably because the forecast in /data/aaron/fbf-candidate/original-data/zambia is Riz' version, which uses the wrong season (NDJ). Please fix that, and send a pull request for the forecast configuration in python_maproom_zambia.
Please add a README to /data/aaron/fbf-candidate/original-data/zambia explaining what the different bad years csv files represent, where they came from, and what command was used to convert them to zarr. (@nitinmagima this probably requires input from you.)
| issue_months: [5, 6, 7, 8] | ||
| start_year: 1983 | ||
| zambia: | ||
| logo: Zambia_IRI_120x48.png |
There was a problem hiding this comment.
@nitinmagima do we have a logo file? If not, we'll use the generic IRI one.
There was a problem hiding this comment.
To use the IRI one, put IRI_128x128.png
| sql: select adm0_code as key, adm0_name as label, ST_AsBinary(the_geom) as the_geom | ||
| from iridb.g2015_2012_0 where adm0_name = 'Zambia' | ||
| vuln_sql: select adm0_code as key, year, sum(vulnerability) as vuln | ||
| from public.fbf_vulnerability where adm0_name = 'Zambia' group by 1, 2 |
There was a problem hiding this comment.
This presumably doesn't work, because there are no rows for Zambia in the fbf_vulnerability table. That will cease to be a problem once the vulnerability layer is removed, but it would be good to merge this sooner than that. See ethiopia for a dummy query you can use instead.
There was a problem hiding this comment.
The vulnerability layer has been removed, so now all we need to do is remove vuln_sql.
2 participants
No description provided.