Cartodb: Option to choose another category ramp

Created on 19 Jul 2016  路  29Comments  路  Source: CartoDB/cartodb

We will need the option to change the category ramp from default to another one in our list.

Right now, I don't see a way to access the color ramps once I've made the selection of Category on a non-numeric field.

screen shot 2016-07-19 at 1 55 37 pm

SMOKE_MG17

SMOKE_MG21

Frontend cartography enhancement

Most helpful comment

HUGE and been waiting a long time for this!!

thanks to all!!!

All 29 comments

Cc/ @urbanphes

Hey! I upload here the complete flow for category ramp selection.

Basically the idea is to replicate the behaviour of the others ramp selection:

  1. You select column
  2. You select color ramp
  3. You need to adjust colors? Then go to custom color set.
  4. Edit

To go back you have a back arrow on the column name. I also added a "Category" distribution but disabled due you cannot change it

UPDATE

Changed "back" labels to its own name, so it can act as a REAL sequential back:
screen shot 2016-07-27 at 15 22 24

Updated back label ^

VAMOS NENO.

nice, @josecruz!

This was a common question/request at the Builder training last week in NYC. Just a heads-up. Think it is really important!

It is already implemented and working.

it is? I'm not able to see the other category ramps. Am I missing something?

screen shot 2016-10-04 at 10 00 16 am

Ahh, wait, you can change the color of any category, and that "ramp" will be stored until you changed to any other column. But yes, definitely not the thing you were requesting.

Ey @CartoDB/design if I push this to RT, are the assets ready to add the other category ramps to BUILDER?

nop, push it :)

@ramiroaznar do we have a ramp list?

Yes, you can find a wiki here. But I suppose, there will be another one in cartocolors repo. Here, for instance.

adding @arianaescobar to the loop in case you need a hand from design

Hey @matallo can any of Bravo team give a hand to @IagoLast?

First working version:

https://gyazo.com/272e055f9ca23eafe1a2d4d4cb1f218b

Got the defaults!

@IagoLast please can you change the defaults:

  • For numbers: PurpOr [BONUS]
  • For categories: Vivid

As explained in this issue https://github.com/CartoDB/cartodb/issues/8857

@arianaescobar can you confirm that PurpOr color ramp for gradient/choropleth maps works for Voyager too?

It does :)

Oops, I might have spoken too soon. The lightest color of that ramp is quite similar to Voyager's land color so the contrast is not ideal. Could we put this one on hold until @makella returns so she can review it first?

By the way, we are also applying this change to lines and polygons, right?

The defaults can wait until Mamata is back (today). :-)

hello all this is so great and a big step forward :)

before I go into the default selections, I am wondering if it is a global default for all geometries (points,lines,polys) or if we have the option to modify the default color scheme based on geometry type.

the old issues that are referenced here (with default selections) are specific to geometry/map types.

let me know that and then i'll provide answers depending on what we are doing.

thanks!

hi @makella! :-) :heart:

We can use this issue to implement the right default ramps by geometry. So please can you tell us the default cartocolors schemes for this cases?

Quantitative ramps:

a. Points
b. Lines
c. Polygons

Qualitative ramps:

a. Points
b. Lines
c. Polygons

?

Looping @alonsogarciapablo

After talking with @makella these are the default color ramps:

Quantitative ramps:

a. Points: Burg
b. Lines: Magenta
c. Polygons: Purp

Qualitative ramps:

a. Points: Prism
b. Lines: Prism
c. Polygons: Prism

The logic behind these changes was:

  • We needed to adapt the default ramps to the new default basemap (Voyager).
  • They needed to work also on topo of Positron and Dark Matter basemaps.
  • (Secondary) Points and lines ramps should work on top of polygons.

Mamata selected the default ramps for points and polys. I took the decision on lines because Steph is on vacations.

Magenta

Prism

@dv343 @elenatorro you can go ahead! Let me know when the acceptance is ready.

@dv343 @elenatorro ping me if you need help :)

image 008

image 007

VAMOS!!!! @IagoLast @elenatorro @davidmanzanares @jesusbotella @matallo

VAMOS!! Well done, team! 鉂わ笍鉂わ笍鉂わ笍

non era sen tempo 馃槀

in production! 馃殌

HUGE and been waiting a long time for this!!

thanks to all!!!

Was this page helpful?
0 / 5 - 0 ratings