A little while ago we announced our partnership with ecoinvent, one of the world's most comprehensive environmental datasets. These data now live in the Data Explorer right alongside the rest of the sources available in Climatiq. Note that access to ecoinvent data requires a paid license - get in touch with us if you like to know more about key environmental datasets like ecoinvent.
Our activity mapping tool now allows batch uploading, meaning you can add a full schema of custom activity labels mapped to Climatiq activity_ids in one go, and start making calls based on your own taxonomy. Stay tuned for more updates to our mapping capabilities, as we are working hard to develop some great new the tricky task of mapping activity data to emission factors.
We now have batch endpoints for the different compute endpoints including memory, CPU and storage. This is handy if you need to perform many computations at once. In other computing endpoint news, the computing metadata endpoint is now out of alpha - you can rely on it being stable between versions now.
We're very pleased to announce that the excellent work our science team do week in, week out is now front and centre in the Data Explorer! Where we have detected a data anomaly, there will now be an alert displayed and an explainer to tell you more about the issue found. Of course, these flags are available in the API so you can listen for them in your implementation.
Our GLEC-compliant freight endpoint (currently in alpha) is now able to route-plan intermodal logistics for road, sea and air. Just put in a geolocation (long/lat, postcode, city name, full address, or just a search query) and select your mode and let the endpoint do the rest. It will plot the route to the nearest port or airport and provide emissions estimates broken down by each leg, including scope 1 and 3 emissions. Just let us know if you'd like to join the alpha.
We're constantly improving our documentation based on your feedback - and after a few calls with users to understand how we can better describe the way LCA activity is handled by the API, we've updated our how-to guide.
You never go very far in the world of emissions assessment without hearing the term "ecoinvent". We've been working with the ecoinvent team to make the huge array of emission factors in their v3.8 dataset available to you via Climatiq's lightning-fast, distributed infrastructure so that you can embed the world's most widely-used materials/life-cycle emissions dataset right into the heart of your decision-making. You will be able to browse the dataset soon via our data explorer; in the meantime, just get in touch with us if you are interested in getting these data into your project.
Those familiar with our flights endpoint already know that it's fantastically helpful to have distance calculations taken care of. Now we're very pleased to be going into alpha with an intermodal version that will estimate road and sea freight emissions from and to any location in the world - whether you have coordinate, city name, postcode or any other type of address or location information. Compliant with the Global Logistics Emissions Council and, logistics movements are estimated in realtime incorporating factors such as traffic data, allowable routes, vehicle/vessel size, road gradient and plenty more. Please get in touch if you are interested in joining the alpha group trialling this new functionality.
Cloud Carbon Footprint (CCF) have released data for 2022 and we've now transformed this into nearly 700 emission factors to help bring your cloud computing measurements bang up to date.
The AIB has also released their 2022 national electricity grid factors for European nations.
Many of you have told us that while the datasets available in the API meet the majority of needs, sometimes there are specific emission factors that are needed for your project that can't be shared publicly - say a licensed dataset or footprints provided from suppliers. So we're very pleased to announce a new feature, available as an add-on to our Corporate or Commercial tier: Private Emission Factors. This feature allows you to add any emission factors to a secure environment via an uploader in our dashboard, making them available to you right alongside any of the currently available emission factors in our /estimate, /batch and /search endpoints. Contact us for more information on getting access to this feature.
We're delighted to announce that the default emission factors from the Global Logistics Emission Council (GLEC) Framework are now available via the Climatiq API. These are ready to use in your freight logistics estimations from today. Stay tuned for more on this front, as logistics is going to be a big focus for the next few months (grab me or one of the team if you want to learn more).
Here they are! Note that, as with any annual data update, any queries that are not specifically calling 2021 will automatically update to use 2022 data. As well as updating their existing factors based on the latest data available, BEIS have for the first time included emission factors for estimating homeworking emissions.
You can now specify a region_fallback boolean for the custom activity, classification and estimate endpoints selector. If this boolean is set to true and your initial estimate fails to find an emission factor specific to the country or region provided, Climatiq will automatically broaden your region to factors with the same ID mapped to regions the country falls within (for example Tanzania → Africa → Global) until it finds a compatible emission factor.
Data quality issues found by our science and data team are now highlighted within API responses. Climatiq has a tiered approach to handling of data quality issues; where emission factors are considered statistical outliers or otherwise seriously problematic, they are not included in the API. However, where the issues are less serious we include the datapoints to provide consistency with the source data, and provide a data_quality_flags in the response. Current flags are erroneous_calculation and notable_methodological_variance; details about the issues detected will be outlined in the description field of the emission factor in question. More details about this feature can be found in our how-to guide and in the data guidance of the OEFDB.
Speaking of how-to guides, we've overhauled our guides page with a new look and feel and added a couple of new guides in addition to the data quality guide above:
The data explorer has been updated to make it even easier to find the emission factor you need, with an update to filters allowing for selection of multiple categories at a time and regions now returning any sub-region of a country that you have filtered to (for example all US states will be returned if you filter to US rather than just US-wide factors).
After having to keep things very hush-hush we can now officially announce that Climatiq is one of just 50 launch apps on Stripe's brand new App Marketplace (announced 24th May). Our Emissions Calculator app allows any stripe merchant to assess the impact of every sale (and their entire sales history) based on GHG Protocol and EPA emission factors. We're very excited to be helping Stripe merchants understand their impact, as well as prompt action through Stripe's carbon removal fund.
.jpeg)
As well as this, we now support over 30 currencies, which will be converted in real-time for spend-based emission estimates.
We also released a number of improvements to our API error handling, including better descriptions of errors to help you understand what might have gone wrong.
Reminder: remember to cut over to the new search endpoint if you haven't already - we will soon be deprecating the emission factors endpoint to provide a much lighter (and more sustainable!) way of assessing the availability of factors.
...all of which takes us past 12,000 datapoints!🚀
We have added the ability to map your own custom taxonomies to Climatiq emission factors right in our dashboard. Just click on the Activity Mapping tool in the dashboard and once you have mapped your taxonomy to emission factor IDs, the custom activities endpoint will accept your own IDs as selectors in API calls. You can have different maps for each of your projects, giving you plenty of flexibility.
A new classifications endpoint has in now in alpha. This endpoint allows you to hand up industry codes (in this first release ISIC4 and NACE2) to the API, meaning activities can be automatically classified and estimated. In addition, as these codes map to each other via the UN correspondence tables, factors that aren't directly mapped to the code passed up can be automatically selected to ensure the most valid estimates are returned. There'll be more classifications to come soon, including NAICS and CPC, making it increasingly easy to get the best emission factor automatically - please do get in touch if there is a particular classification you would be interested in seeing supported.
The new search endpoint was released to replace the deprecated list emission factors endpoint to provide a much lighter way of assessing the availability of factors (please do move to the search endpoint if you are still using the list factors endpoint).
Since our last release notes we have:
Only rarely do we ship "versioned" releases, preferring to release continuously to prioritise getting our data and tools into your hands. However in this instance we have a range of exciting updates which involved the potential to break or interfere with existing implementations. Before we get to the details of the release, it's worth mentioning that we have published a handy migration guide to step you through switching from v2 to v3 - and don't worry, v2 will remain supported while you do. We intend for this to be the last beta release before we go into full production.
There's a lot there, so plenty of additions have been made to the docs page to help take advantage of the new functionality, including as mentioned the handy migration guide (note you can switch back to the v2 docs page using the selector in the sidebar).
We hope you had a chance to take some time to reflect on the past 12 months and to revive as we go into a huge year for tackling the climate crisis - 2022 feels make-or-break.
Here at Climatiq, while we’ve relished the chance to take stock, we haven’t slowed; we’re starting 2022 with a bang by announcing the addition of almost 400 spend-based EPA emission factors to the API. Having a dry January? Why not find out how much carbon you’re saving - now according to data release by either the UK or the US government.
There’s a very serious side to this of course - assessing supply chain emissions is a huge problem for companies, and while spend-based data isn’t perfect, in many cases it’s the only viable way of reporting. As such, the UK and US data will soon be joined by the high-level global numbers used by the GHG Protocol scope 3 calculator.
Want to make sure these numbers are comparable? We’ve got you covered: the Climatiq API provides currency conversion on the fly, based on the average rate of the year the emission factor was reported.
That’s not all of course - as ever, there’s a range of data and functionality additions since our last release communication, which you may already be using. In case you missed them:
Led by feedback from you, our beta community, this release includes a bundle of exciting updates. There's lots of detail on what has been updated and why in our release blog post, but here are the key things to know. We've:
These updates represent a significant improvement in both technical usability and in data quality and robustness. Above all, it sets us up for fast iteration in both including new emission factor data (look out for spend-based scope 3 factors soon) and rapid development of features in the API.
To take advantage of the new features and dataset you will need to update your queries based on the new version of the implementation docs available at docs.climatiq.io (but don't worry we still support the old version, so nothing will break).
