Beginning with the release of January 2024 data, Google Cloud Carbon Footprint will adopt a biannual methodology refresh schedule, with updates planned for January and July data releases each year

## Change Beginning with the release of January 2024 data, Google Cloud Carbon Footprint will adopt a biannual methodology refresh schedule, with updates planned for January and July data releases each year. For the January 2024 data release (in mid-February 2024), we have made the updates below and updated carbon model to version 10: Data accuracy: * Improve internal machine-level power readings for storage machines. Update allocation of energy from some machines, improving Bigtable data accuracy. * Further improve mapping between Google Cloud services and internal resource use, particularly for a few Networking SKUs. * Improve Google Cloud region defaults and coverage. [location.location/location.region](https://cloud.google.com/carbon-footprint/docs/data-schema) with former `NULL` values are defined as `global`, and we improved data for the `europe` multiregion. Corporate data input refresh: * Update Scope 1/3 apportionment factors using latest Google company-wide data from [2023 Google Environmental Report](https://www.gstatic.com/gumdrop/sustainability/google-2023-environmental-report.pdf). See the [Non-electricity emission sources section of methodology document](https://cloud.google.com/carbon-footprint/docs/methodology#non-electricity-allocation) on how we apply these apportionment factors. Service coverage: * Reintroduce App Engine and GKE Enterprise/GDC services [(formerly Anthos/GDC-V)](https://cloud.google.com/anthos/docs/concepts/overview), as internal data mappings have been improved. * Remove Looker, Apigee, Chronicle, and AppSheet from [covered services](https://cloud.google.com/carbon-footprint/docs/covered-services) of Carbon Footprint, due to potential mis-attribution of carbon to these services. We are actively investigating and working on the improvements. Once internal data mapping improves for a service, we plan to add it back.