You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen the recent developments towards the Taxonomy v3.3. We noticed that many new occupancy types have been added and we are happy to see that.
Until now, we have worked with our own extended version that contains a similar selection of extended occupancy types that we are able to distinguish in the data we are using. We noticed that many of our extended tags have now been added in v3.3, which is great! Some of our tags we cannot find in v3.3 and simultaneously we think that we may also use some of the newly created tags in v3.3 for our purposes. You can find our proposal for a new occupancy definition here:
We also have a Python library to handle taxonomy strings (based on v3.2) to a certain degree (limited to the existing taxonomy strings in the open GEM exposure models, but not yet covering every possible tag from the v3.2 definition). You can find this library at:
To prevent double efforts and a possible split in definitions, we suggest to coordinate this work and to try to combine the best of both worlds into the new version of the GEM Taxonomy.
Thanks for sharing the details on the taxonomy occupancy. We will review the files and compare with the v3.3 modifications, and explore ways for joining efforts.
Hi,
We have seen the recent developments towards the Taxonomy v3.3. We noticed that many new occupancy types have been added and we are happy to see that.
Until now, we have worked with our own extended version that contains a similar selection of extended occupancy types that we are able to distinguish in the data we are using. We noticed that many of our extended tags have now been added in v3.3, which is great! Some of our tags we cannot find in v3.3 and simultaneously we think that we may also use some of the newly created tags in v3.3 for our purposes. You can find our proposal for a new occupancy definition here:
proposal_extension_GEM_Taxonomy_v4_occupancy.xlsx
We also have a Python library to handle taxonomy strings (based on v3.2) to a certain degree (limited to the existing taxonomy strings in the open GEM exposure models, but not yet covering every possible tag from the v3.2 definition). You can find this library at:
https://git.gfz-potsdam.de/globaldynamicexposure/libraries/taxonomy-lib
To prevent double efforts and a possible split in definitions, we suggest to coordinate this work and to try to combine the best of both worlds into the new version of the GEM Taxonomy.
Cheers
Danijel & Laurens (@LaurensJN)
The text was updated successfully, but these errors were encountered: