As an analyst I want to see a calculated quantity for emissions using AR5 GWP values so that I can compare older years values with the updated GWP

[dleard]

A new column in the swrs.emission table is required to allow analysts to see what the calculated quantity for previous years would be according to the updated AR5 GWP values .

As an analyst When I am querying the swrs.emission data in Metabase I can see an AR5 calculated quantity value which is calculated by quantity x gwp(AR5 value)

Development steps:

• add a GWP table to the swrs_parameters schema with the updated AR5 GWP values
• The GWP table should have all gas_type values in the emission table (can be found in metabase). This is how we will join emissions to gwp
• Each gas_type row should have an associated AR5 GWP value
• add a numeric column to the swrs.emission table ar5_calculated_quantity
• in the load function for swrs.emission, use the quantity value from emission and the GWP value from the GWP table (by joining on emission.gas_type = gwp.gas_type) to calculate the ar5_calculated_quantity column

[dleard]

Hey team! Please add your planning poker estimate with Zenhub @BCerki @gurjmatharu @JoshLarouche @sam-warren @Sepehr-Sobhani

[dleard]

Please add your planning poker estimate with Zenhub @mikevespi

[pbastia]

@BCerki the ar5_calculated_quantity column is null in Metabase-dev, when the quantity is filled out. I also can't see a swrs_parameters schema in the swrs database. Maybe something went wrong in the deploy to -dev?

[dleard]

@BCerki @pbastia The dev data is entirely synthetic, created with inserts rather than parsed via the ETL (where the ar5 calculation is done) so the calculated field will always be empty in dev. The pgTap tests covered the load() function and passed, I suggest deploying this to test where I believe the ETL does run over a few reports and the value should show up there.

[pbastia]

Aaaah thanks for clarifying. I thought we had fake XML that got parsed. Seems like we can't test in dev then