Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the TaxTweb to GEM Taxonomy v3 #28

Open
raoanirudh opened this issue Jun 5, 2019 · 5 comments
Open

Update the TaxTweb to GEM Taxonomy v3 #28

raoanirudh opened this issue Jun 5, 2019 · 5 comments

Comments

@raoanirudh
Copy link
Member

The TaxTweb is a very useful tool for obtaining validated short taxonomy strings for building types. The current string outputs, however, are still based on the older GEM Taxonomy v2. The current version of the GEM Taxonomy, v3.x / Multi-hazard Taxonomy, was released in March 2018. While most of the attributes remain unchanged, there are a few changes. It would be really helpful if the TaxTweb could be updated to support the new GEM Taxonomy.

cc: @CatalinaYepes

@pslh
Copy link
Member

pslh commented Jun 5, 2019

Note that this implies changes also to the Taxonomy glossary, the IDCT data collection tool and possibly to other software tools (ipython notebooks, risk toolkit?).

@CatalinaYepes
Copy link

I think we should assign some time to do this. The models in the GRM are using the latest version of the taxonomy. The document generated for GED4ALL is the starting point to do the modifications and add the additional descriptions to the Taxonomy glossary. I don't think at this point we need to modify IDCT (there are other type of improvements that have not been done and have higher priority).

@pslh
Copy link
Member

pslh commented Jun 26, 2019

See also gem/oq-platform2#89

@nicolepaul
Copy link

nicolepaul commented Jul 14, 2023

I agree with the others on the Risk team that it would be worthwhile to assign some time to this. Additionally, we could improve our unit tests / create utility functions for exposure modellers to conform to GED4ALL if this work is completed. At the moment, our exposure models are inconsistent.

@raoanirudh
Copy link
Member Author

See also gem/global_vulnerability_model#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants