topic Re: Deneb - change labelFontWeight for one value in an axis label in Custom Visuals Development Discussion

Deneb - change labelFontWeight for one value in an axis label

tomwill — Tue, 07 Feb 2023 18:45:08 GMT

I have a text field ['Region'] with four values {Global, AMER, APAC, EMEA}. I have a simple bar chart and want the label to be bold only for 'Global'. I tried:

"encoding": { "y": { "field": "Region", "type": "nominal", "axis": { "offset": 10, "title": null, "labelFontWeight": { "condition": {"test": "datum['Region'] == 'Global'","value":"bold"}, "value":"normal" }

but there is no change to the label font weight. What is interesting is that I switched the result conditions, making the '==Global' "normal" and the else "bold" and it changed font weight on all the labels to bold. That leads me to believe that my condition is never being evaluated as true. Any ideas why? Is what I want to do - changing a signal value in an axis label - possible?

Re: Deneb - change labelFontWeight for one value in an axis label

dm-p — Tue, 07 Feb 2023 20:20:33 GMT

Hi @tomwill,

Fields are not exposed in the datum object for an axis label. You have access to either a label or value property in the backing datum and it's this that you need to inspect in your condition.

Something like the following should work:

"labelFontWeight": { "condition": { "test": "datum['value'] == 'Global'", "value": "bold" }, "value": "normal" }

I've replicated this in a chart I have open, specifying that the Wellington label be bold, as per the above approach and this seems as expected, e.g.:

Regards,

Daniel

Re: Deneb - change labelFontWeight for one value in an axis label

tomwill — Wed, 08 Feb 2023 21:17:25 GMT

Thanks this worked. Very new to Deneb so still a lot of copy, paste, pray. I had used the

"datum['Region']

structure to change data labels based on value but must be a difference in how datum works in a 'mark' block vs and 'encoding' block.

Re: Deneb - change labelFontWeight for one value in an axis label

dm-p — Wed, 08 Feb 2023 21:31:42 GMT

Glad it worked! Normally you would be correct in your assumption - you would refer to the field in a datum whenever it typically makes sense to do so (i.e. in a mark or most encoding channels), and was a good place to start. I was caught out by this initally, too 🙂

Axes are a special case because they potentially represent the normalisation of multiple series for a category, or could be continuous (and therefore use a different granularity for the number of displayed ticks than there are in your series). As such, the axis labels have their own (simpler) datum structure that is derived from the field you've encoded.