🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Pyrite | Level 9

## Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

Hello all,

is there any option to add to this code, so that small values are not summarised as other in my pie chart?

```legend1 label=none
shape=bar(4,1.5)
position=(top left)
offset=(5,)
across=1
mode=share;

proc gchart data=mydat;
pie var1 / sumvar=cases
coutline=black
value= inside
slice=arrow
percent=outside
legend=legend1;

run;
quit;
```
1 ACCEPTED SOLUTION

Accepted Solutions
SAS Super FREQ

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

Set OTHER=0 on the PIE statement.

5 REPLIES 5
Diamond | Level 26

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

Small values of variable CASES? Small pie slices? What is your definition of "small"?

--
Paige Miller
Pyrite | Level 9

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

@PaigeMiller Hi, I mean both situation, because small values of variable cases automatically draws small pie slices

Diamond | Level 26

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

You would have to filter the data before you create the PIE chart, so that PROC GCHART is not working on the full data set, but it is working on a data set where you have removed the small values and/or small slices.

--
Paige Miller
SAS Super FREQ

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

Set OTHER=0 on the PIE statement.

Meteorite | Level 14

## Re: Values less than or equal to percent-of-total shouldn't be summarised as Other gchart(pie)

Do you want small values to not be shown at all? Or do you want small values to stay in their own slices, rather than being summarized into the automatically generated 'Other' slice? (there are 2 answers above in previous comments - one for each of these scenarios)

Discussion stats
• 5 replies
• 326 views
• 2 likes
• 4 in conversation