2021| July 6 - Kickoff 1
Climate Action Data 2.0 Meeting #1 Agenda
(July 7 at 8am PDT / 11am EDT / 4pm BST)
Agenda
· Introductions
· Presentation: Climate Action Data 2.0
· Guided discussion:
o What do you think about the working group streams/structure?
o Should there be other groups/people that should be involved?
o What other questions should we ask?
o Who would like to co-convene the ‘use-case’ group?
· Timeline/upcoming plans/milestones
· Discussion on use-cases & policy relevance
· Closing remarks
Meeting notes
Evolving Themes of the first CAMDA call 7/7/2021
· Interest in organizing multiple CAMDA (COP) events
· Relevance and focus of the global south
· Mapping of the diverse data landscape - understand who has what kind of data and how we can harmonize
· Engage with policymakers on the importance of quality climate action data
Events planning
· Potential to merge COP side event with DDL - Interested merge parties to connect with Angel afterward
· Discussion on COP event slot that is reserved for the CAMDA community depending on whether this is a closed or open event
· Opportunity to participate via the UNFCCC dedicated to resilience frontiers for those members in the group that are more working on the adaptation side
· Todd - if we are able to organize this group sufficiently before COP, we could also try to have an event at the high-level champions meeting
o CAMDA is launching additional working groups on “Finance” and “Resilience and Adaptation”
Workstream feedback
· “Data Robustness and Quality” - this fits across a couple of streams, as well as “what data is missing? Do we collect everything we need to?” Resilience data as well so we’re not missing half of the world
· The need to be talking about multi-level governance here, but there is a political component here as well that we should all be aware of - how do we pressure countries to step up their game?
o Importance of including the global south.
· Linkage/contribution to the state of climate action report people (WRI) - to address: what are the most policy-relevant pieces each year?
UNEP Emission Gap - transformation tracking, data overview, close coordination between data providers and consumers
· Consider a public call with the weight of all of the organizations here to create an open-source resource of all of the datasets out there and allowing organizations to create connections in and outside of this network. Make sure that we’re not talking just to ourselves and inviting others into our living rooms, but rather completely opening-up
· Angel: we want to highlight some of the key problems within each area - we also have some ideas around what action items might be but these are not set in stone (Martin’s slide)
· Reflection of how do we take into account what is happening with the global south?
o It’s not that the data doesn’t exist, it’s that we don’t have access
o What is the impact of failing MRV systems?
o Angel: Global south issues and focus should be a thread across all of the workstreams
· Would be great to have an overview on what kind of data is available from everyone in the group here, and what kinds of data will be coming into availability over the coming months/years/etc.
· Perhaps we can record on gitbook metadata of all our resources, existing and planned?
· Angel: Hopefully convene a data harmonization working group meeting at the end of July
· You’re never comparing apples to apples - even if the dataset is available, there is a huge issue with making them compatible. Identifying which power plant is the same power plant across datasets is a huge issue for example.
· We have all this amazing data but not a lot of people know about the data - so doing targeted outreach is actually very important as well
· We want to bring datasets from the domain experts which can be used as benchmarks etc. to bring to the machine learning experts to utilize
· We are in the foothills of this right now - it’s important to communicate to the policy world on how the work here, as well as accountability + transparency framings are necessary for the global work around Climate Change action.
o In the past you might have private corporations saying that “we can’t do this, we don’t think that it is important to have full transparency” - now the move is that they’re hiding behind trade groups to avoid transparency concerns.
· Significant gap in data reporting and data availability between north and south - we have noticed reporting fatigue
o Getting people together outside of this community would be something that governments would also like and support I think
o As we’re talking about net-zero and re-calibrating ambition, there is a massive desire to get the data to be up to date and assess progress now rather than waiting a longer period to assess progress
First Data harmonization meeting will be at the end of July/beginning of August
First order of business will be a massive accounting exercise of metadata - what are we working on, what is available, what is the landscape
Thinking about potential users and who might have needs and demands for some of the harmonized data we are working with
Digital Infrastructure/Architecture - first meeting is to be held before the end of the month.
Looking at the entire data trail - data collection, sensors, how data ends up being available or stored in databases
Datasets are more than just data, they’re an embedded accounting strategy
Martin brings up a collective visioning exercise for the next meeting
Future visioning exercise (what would the future look like) - visual board of our ambition
Data trail (collection, sensors, raw data database flow, cleaned, trusted APIs, different technologies, signing data sets), minimizing compiling efforts, what are data sets
Feeding into accountability, costs and time resource, technical and political tensions, automated way
Todd:
This as an umbrella strategy across the workstreams is intended to include the strategic comms and outreach people, even though there is no specific group set up for it - but these people will likely live in the Policy/Use Cases group
Anyone interested in leading the policy/use cases group should connect with Todd
Last updated