Similar Actor Comparison
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- react, typescript
- Ambito
- data-visualization
Direzione di ricerca
Start at the actor explore page and inspect the Level card to understand how it selects an actor’s latest emission value from the highest rated source. Then trace where actor parent relationships and population data come from; done means a widget compares the selected actor with the closest-population sibling and a similar actor under a comparable parent, showing source, year, actor and parent names, and N/A when required data is missing.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem Statement
It is hard to understand if an actor is emitting more or less than what other similar actors are doing, this should be easy to map with data from other actors
Who is affected by this problem
Funders, researchers, advocates, that want to see who should be encouraged to improve their current emissions, or looking for cases to highlight for best practices.
What is the problem
It is hard to understand if an actor is emitting more or less than what other similar actors are doing, which is an obstacle when understanding which actors should be more incentivized to reduce emissions, or which actors to use as best practice cases
Where does the problem occur
This occurs in the actor explore page
When does the problem this occur
This occurs when users are looking for emissions and progress data in the actor explore page
Why does the problem occur
This occurs because currently only data is shown for a particular actor but with no easy way to see at the same time how that actor compares to other similar actors of the same type (it is easy to see how the actor compares to its “parent” and “child”
Feature Description
Build an independent widget that shows emission and contextual information for similar actors:
-
Comparison 1: Same parent actor
- Show emissions for the actor from the same "parent" that is closest in population to selected actor
- Example: if selected actor is British Columbia (Canada), show Alberta, which is closest in population from Canadian provinces
- If no population data for other actors from the same parent, then show "N/A"
- Emission value should be the same one that is shown in the Level card
- i.e, the the latest emission value from the highest rated source
- If no emissions data exists, show N/A
- Show emissions for the actor from the same "parent" that is closest in population to selected actor
-
Comparison 2: Similar parent actor
- Show emissions for the actor from another "parent" that has is closes in population to selected actor's parent, that is closes in population to selected actor
- Example: if selected actor is British Columbia (Canada), show Mazowieckie (Poland), because Poland and Canada are close in population and Mozowieckie and British Columbia are close in population
- If no population data for actors from the similar parent, then show "N/A"
- Emission value should be the same one that is shown in the Level card
- i.e, the the latest emission value from the highest rated source
- If no emissions data exists, show N/A
- Show emissions for the actor from another "parent" that has is closes in population to selected actor's parent, that is closes in population to selected actor
Goal: What do we want to achieve with this
Make it very straightforward for users to understand the historic emissions of an actor based on selected source
Benchmarks
https://climatetrace.org/inventory?sector=all&time=2021&country=CAN&gas=co2e100

We want to know the source and year for the emissions data, and actor name and parent actor name
Evidence of problem
User interviews and comments from partners
- Lingua principale
- TypeScript
- Stelle
- 64
- Fork
- 16
- Merge medio
- 1h 1m
- PR unite (30g)
- 2
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Open-Earth-Foundation/OpenClimate
-
Update PRIMAP data 2.6Apertadata upgrade
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
-
Update CEADs dataApertadata upgrade
Difficoltà 3/5 1-2 giorni Idoneità per principianti 38/100
-
data upgrade
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
-
data new
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 10/100
Tutte le issue di Open-Earth-Foundation/OpenClimate
Issue simili
-
account bug communication lecture
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
area:tui bug platform:macos
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
anthropics/claude-code#109005 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
openedx/end-to-end-tests#196 ·
I maintainer di solito rispondono entro 1 giorno
-
area:tooling good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
interledger/publisher-tools#1007 ·
I maintainer di solito rispondono entro 1 giorno
-
priority/medium roadmap/v1.1.1 stakeholder/rapr type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
databrickslabs/ontos#1420 ·
I maintainer di solito rispondono entro 3 giorni