Carbon Flux Model v1.3.2 with Updated Drivers (4/2/24)

[melrose-wri]

Updated the uris in the raster-catalog-default.json with the newest versions of the carbon flux model emission, net flux, and emission node code outputs.

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• [ ] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [x] Check the commit's or even all commits' message styles matches our requested structure.
• [x] Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation content changes
• [ ] Other (please describe):

What is the current behavior?

Previously used the emissions and net flux datasets from our previous 1.3.2 carbon flux model run which used an incomplete version of the drivers of tree cover loss data.

Issue Number: N/A

What is the new behavior?

Updated the uris for the following layers in the raster-catalog-default.json:

• gfw_forest_flux_full_extent_gross_emissions_co2_only_biomass_soil
• gfw_forest_flux_full_extent_gross_emissions_non_co2_biomass_soil
• gfw_forest_flux_full_extent_gross_emissions_co2_only_soil_only
• gfw_forest_flux_full_extent_gross_emissions_non_co2_soil_only
• gfw_forest_flux_full_extent_net_flux
• gfw_forest_flux_gross_emissions_node_codes

Does this introduce a breaking change?

• [ ] Yes
• [x] No

Other information

N/A