search

carbon-budget-explorer / cabe

Web application to explore carbon budgets
Apache License 2.0
1 stars 0 forks source link

Colors #109

Closed MarkMDekker closed 7 months ago

MarkMDekker commented 7 months ago

Reconsider coloring. Maybe based on ELEVATE color scheme. I will check with Isabela.

MarkMDekker commented 7 months ago

Isabela shared this with me, which we can use to colour everything. But maybe not a priority for beta version?

Visual identity.pptx

MarkMDekker commented 7 months ago

In the World map, could you also narrow the 2030 to [0, 20] and the 2040 axis to [-5, 10], or something that you see fit? @lvreedenburgh I know Peter already worked on this a lot (thanks!), but let's polish it one step further. If you have suggestions for better colormaps, that's of course great.

MarkMDekker commented 7 months ago

On the question where we should apply these colours... I think mainly the "green" curve on the global pathway page (also associated with the sliders), and the background dark-blue in the top bar and intro page. As soon as those are fixed, we can re-think what to do with all other colour instances.

MarkMDekker commented 7 months ago

On the world map, see my comment from 30 min ago.

MarkMDekker commented 7 months ago

Extras are I think, for example, changing the bright-red from the current policy projections.

MarkMDekker commented 7 months ago

@lvreedenburgh colours of the effort-sharing principles can be found in src/lib/principles.ts

lvreedenburgh commented 7 months ago

Hi Mark, it is taking me way too long to find out where the colors are defined for the top bar and sliding bars.

I'm also having internet issues, so that's great.

Also, could you explain a bit more what you mean with could you also narrow the 2030 to [0, 20] and the 2040 axis to [-5, 10]?

Peter9192 commented 7 months ago

Also, could you explain a bit more what you mean with could you also narrow the 2030 to [0, 20] and the 2040 axis to [-5, 10]?

The domain limits are calculated in the web service: https://github.com/carbon-budget-explorer/cabe/blob/49c333dfa175dc9bdee0ad2f76badc2230f287b8/ws.py#L338-L342

I think @MarkMDekker's suggestion is to hardcode them instead of calculating based on data, right? Not sure how I like that for good, but temporarily it could be okay. Maybe add an inline comment to undo that later?