Closed light-and-salt closed 7 years ago
Here's a scenario where I want to use the raw domain. When I have multiple visualizations of the same data set on the same screen (e.g. in narrative visualizations, in visualization recommender systems), I want the color mappings to be consistent across visualizations. Therefore I always want to set the domain
of the color scale to raw
.
@domoritz will this be easy or hard to do?
The right question is how would this affect the transform order we discussed earlier
So you want it to be pre-filter and also pre selection filter? I'm not sure whether we are putting too much configurability into Vega-Lite with this.
On Fri, Apr 29, 2016 at 6:33 PM Kanit Wongsuphasawat < notifications@github.com> wrote:
The right question is how would this affect the transform order we discussed earlier
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/vega/vega-lite/issues/1327#issuecomment-215898733
I'm not surewhether we are putting too much configurability into Vega-Lite with this.
Well, it's not extra level of configurabililty. This discuss doesn't add new config, but rather discuss how existing config should behave.
Well, it's not extra level of configurabililty. This discuss doesn't add new config, but rather discuss how existing config should behave.
My comment was regarding the option to change the behavior of inlcudeRawDomain.
Concerning the default. I don't think there is a clear preference for either behavior.
Trying the new quick filter UI and I feel very strongly that useRawDomain should be pre-filter.
(Otherwise we're moving quick filter and scale domain changes!)
// only applied to aggregate table
fieldDef.aggregate &&
Hmm Tableau is actually NOT doing this, so I'm not sure about this anymore.
I think we can just explain in the docs that this is only applied after filter and close this issue?
In a high level grammar, if something is named raw
then a user would probably expect it to be raw. Otherwise includeFilteredDomain
could be an acceptable name.
Closing in favor of #1656
Should
filter
affect the raw data domain? Right now, if I set bothtransform.filter
andconfig.scale.includeRawDomain
in a Vega-lite spec, I get the filtered data domain instead of the raw data domain.For example, if I filter out
Europe
and setincludeRawDomain
totrue
, I no longer haveEurope
in my legend. This suggests that thecolor
scale has the filtered data domain instead of the raw data domain.Similarly, filtering on![filter_x](https://cloud.githubusercontent.com/assets/822034/14908919/65328fec-0d92-11e6-9acf-694e7aced16c.png)
Horsepower
and settingincludeRawDomain
totrue
also gives me the filtered data domain.Can we make the raw domain pre-filter so that we can always get the raw domain when
includeRawDomain
istrue
?