WEBVTT 00:00.000 --> 00:13.600 All right, great. Hi, everyone. My name is Evan Podromo, and I'm here with my colleague, 00:13.600 --> 00:19.740 Melon Grunner. We're from the Open Earth Foundation. Open Earth Foundation is a nonprofit 00:19.740 --> 00:27.780 established to make open source software to fight climate change. And we're here to talk 00:27.780 --> 00:33.900 about city catalyst, which is our flagship product for building greenhouse gas inventories 00:33.900 --> 00:34.780 for cities. 00:34.780 --> 00:45.220 All right. So, first off, what is the greenhouse gas inventory? Basically, it's a climate 00:45.220 --> 00:50.300 accounting tool that allows you to catalogue all greenhouse gas emissions within a city, 00:50.300 --> 00:55.820 at least in our case. It's sorted by the different sectors and sub-sectors, different 00:55.820 --> 01:02.140 gas as well, the different scopes, so inside or outside of the city boundary. And it's 01:02.140 --> 01:06.780 basically a list of highly modern emissions, highly modern estimates of emissions that are 01:06.780 --> 01:11.780 based on activities that are occurring within the city. All of this is defined by a 01:11.780 --> 01:18.020 standard specification called the GPC or the GHG protocol for cities. 01:18.020 --> 01:24.220 All right. And why all of this matters at all is the only way we can really reduce the 01:24.300 --> 01:29.540 emissions worldwide is by reducing the activities. And this emissions inventory that we 01:29.540 --> 01:34.460 are creating here allows the city to know where that it could apply to the funding best 01:34.460 --> 01:41.420 and fund new programs in order to reduce them. Really there's no point in investing in reducing 01:41.420 --> 01:45.860 emissions from sources that barely affect your cities, so it's really good to know where 01:45.860 --> 01:48.780 you want to focus your resources. 01:48.780 --> 01:53.340 The emissions inventory is also a necessary first step for cities to get financing for climate 01:53.380 --> 01:55.940 action, so they're really important in the darkway guards. 01:55.940 --> 02:01.740 I'm just going to take a closer look at my view, we hold the clicker. So as we said before, 02:01.740 --> 02:08.700 about 70% of worldwide emissions come from cities, so very high amount of our worldwide 02:08.700 --> 02:15.460 emissions come from cities, but only 5% of cities are have a published greenhouse gas 02:15.460 --> 02:21.500 inventory. And that's because it's challenging to put together a greenhouse gas inventory 02:21.540 --> 02:27.420 to obtain the data necessary to publish information for all the different sectors, whether 02:27.420 --> 02:34.140 they're stationary energy or transportation, wastewater, agriculture or industrial. It also 02:34.140 --> 02:42.780 takes a lot of skill and time to put together the systems, be able to drive the necessary 02:42.780 --> 02:49.500 outputs from the input data. 02:49.500 --> 02:51.900 Good, no matter. 02:51.900 --> 02:56.900 Okay. 02:56.900 --> 03:05.740 So what we're doing here to overcome it is we built a web app to allow you to create GHD inventories. 03:05.740 --> 03:10.940 This is a web front end, basically a shared repository for inventories and also for user 03:10.940 --> 03:17.580 data that can be used for collaboration. It's also a data warehouse for GHD related data 03:17.580 --> 03:25.260 organized by city. And we have a separate so-called global API that makes it easy for this 03:25.260 --> 03:31.340 web front end to import only the relevant data, so only for your specific city, let's say. 03:31.340 --> 03:40.140 As well as guided input system that can be used to consider here. If there's no third 03:40.140 --> 03:44.780 party data available, and you need to enter the data that you get from the say your energy 03:44.780 --> 03:50.220 companies and so on manually. 03:50.220 --> 03:59.020 So for the implementation, we have built this using a bunch of different open source libraries. 03:59.020 --> 04:05.340 So for instance, it is built on React, TypeScript, it's next JS, for the IW using track 04:05.420 --> 04:13.660 UI in the back end, it's using standard postpress database and then the SQLize or M to connect 04:13.660 --> 04:19.500 to it also we're using authjs to make the authentication easier and standardize it and 04:19.500 --> 04:25.020 then smaller libraries like Neville for charts, pigeon maps for the city map, sort of validation 04:25.020 --> 04:30.380 I18 next for internationalization because this is already available in three different languages. 04:30.380 --> 04:33.740 And in the back end, let's say decimal JS in order to have precise calculations. 04:35.180 --> 04:38.780 The back end itself is also part of the same next JS application, 04:38.780 --> 04:42.860 order to facilitate a sharing of types of conditions and also functionality with the front end. 04:43.900 --> 04:48.780 And the separate global API that we built for accessing data sources, 04:50.380 --> 04:54.060 that is there that different city catalyst instances can connect to. 04:54.060 --> 05:00.220 It's built on Python, face the fast API, the postpress database again, and the post GIS 05:00.380 --> 05:05.340 systems, so we kind of geometric primitives on the globe. 05:06.460 --> 05:10.460 Then the last part is the data pipeline that imports all of our huge data sources 05:11.020 --> 05:15.980 that's built using Python pandas and MATI and the process of those data sources into the 05:15.980 --> 05:18.780 GPC standard so it can be grouped by individual cities. 05:21.420 --> 05:27.580 And what we get out of that is a mechanism that makes it very easy for even 05:28.540 --> 05:32.860 untrained city personnel to put together their first climate inventory. 05:32.860 --> 05:37.820 We're doing a first pilot project in Brazil with 50 cities in Brazil. 05:38.780 --> 05:42.860 They're putting together their first JS guys or first greenhouse guys. 05:43.660 --> 05:49.900 Oh yeah, thanks. First JS, yes, thank you. First JS, first JS, first climate action plans, 05:49.900 --> 05:54.540 as well as climate change risk assessments using the city catalyst platform. 05:55.500 --> 06:02.780 We collaborate with local consultants in order to identify relevant data sources, 06:02.780 --> 06:07.020 but that we bring them into the platform to make them publicly available to any city. 06:08.060 --> 06:15.500 And we are playing to expand this program in Brazil and also bring it to other cities around the world. 06:17.900 --> 06:21.500 All right, and we are using an 06:21.500 --> 06:25.900 open source, we are an open source repository. So you are all welcome to contribute. 06:25.900 --> 06:30.460 First off, of course, just creating issues on GitHub helps, reporting bugs, proposing features. 06:30.460 --> 06:34.540 You can open more requests in case you familiar with TypeScript and React and want to help out. 06:34.540 --> 06:38.940 Or just reach out to us, give us feedback, let us know where you would like to use this. 06:38.940 --> 06:45.660 This due accordingly is to our repository, but it's also linked in the talk information. 06:46.220 --> 06:48.300 All right, any questions? Thank you. 06:52.460 --> 06:56.460 You want to take questions for? 07:02.460 --> 07:06.940 Yeah, so we are using a lot of remote sensing data, particularly satellite information. 07:06.940 --> 07:12.940 So the satellite regularly takes screenshots or photos of areas, and then you can sort of estimate 07:12.940 --> 07:17.180 by the amount of smoke that is coming out of factory, let's say, how much emissions there could be. 07:17.180 --> 07:20.460 So we're using a lot of open data sources that can be made available to the city there. 07:22.460 --> 07:30.940 But the data sources really vary widely, we can use data that's based on fuel sales within the city. 07:30.940 --> 07:37.660 And we can use that in order to estimate how much fuel was burnt for different processes. 07:38.380 --> 07:45.500 We may have industrial data, we do use satellite data for things like agricultural changes. 07:45.500 --> 07:53.260 Right, so if crops have changed or forests have been deforested, we can actually detect that with satellite data. 07:53.260 --> 07:57.660 We don't do a lot of that data work ourselves. 07:57.660 --> 08:03.100 There are a number of really great projects like climate trace, the IEA publishes data, 08:03.980 --> 08:11.420 at Garp publishes data, we tend to take that data and chop it and slice it so it works for the individual cities. 08:12.540 --> 08:14.300 Great question, thank you. 08:14.540 --> 08:15.260 Yes, in the back. 08:22.300 --> 08:23.180 What kind of entity? 08:27.980 --> 08:32.700 Yes, sure, the question is, what kind of entities are using city catalyst right now? 08:33.340 --> 08:39.420 Yeah, so I think I had it in the previous one, we're working with a pilot project in Brazil 08:40.380 --> 08:44.380 with the Brazilian government and 50 cities in Brazil. 08:45.820 --> 08:54.140 I know that there are other users around who are doing pilot projects, but we don't have 08:54.140 --> 08:59.980 tracking, so we're not exactly sure who else. Is that a fair answer? 08:59.980 --> 09:07.340 Yeah, I think our target audience is really city governments or consultants in the climate space. 09:09.820 --> 09:11.820 Yes. 09:26.620 --> 09:30.220 Yeah, so that's where it really breaks down by scope. 09:30.940 --> 09:38.220 Yeah, sure, the question is, are greenhouse gas inventory just about the gases that are emitted within the city 09:38.620 --> 09:42.460 or does it cover economic activity within the city also? 09:42.460 --> 09:47.100 And the answer is yes, it covers economic activity that happens within the city. 09:47.100 --> 09:55.740 There are three scopes that we call them. Scope one is for fuel that's burned within the city. 09:55.740 --> 10:00.940 Scope two is for energy that's used from power generation and then scope three is for 10:00.940 --> 10:06.220 economic activity that happens outside the city. That's it for us. Thank you very much. 10:08.220 --> 10:12.220 Thank you very much.