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
Now the question is, whether we want to update the Exposure Table to include HW_POPULATION_DENSITY_CLASS and HW_EXPOSEDQUANTITY or not. If yes, the changes to the EMIKAT View and Table have to be implemented by @humerh and @therter as described above. If not, we can leave it as it is.
BTW, I noticed a big difference between POPULATION_TOTAL and HW_EXPOSEDQUANTITY. It this o.k.?
As suggested by @mattia-leone in clarity-h2020/csis#154 (comment), the columns HW_POPULATION_DENSITY_CLASS and HW_EXPOSEDQUANTITY have to be made available in EMIKAT View Exposure data (Population) calculated from EMIKAT so that we can show them in the Exposure Table and Map, which ATM just provides POPULATION_TOTAL as HW exposure parameter.
Once this is done, @therter can update the respective resource specification on CSIS-DEV to make the new layers available on the map and update the Exposure Table so that it shows the new columns.
The text was updated successfully, but these errors were encountered: