topic How to replicate functionalities from vbar with barchart in Graphics Programming

How to replicate functionalities from vbar with barchart

TSAS2 — Thu, 29 Jun 2023 16:25:25 GMT

Hi all,

Normally I am using VBAR from the SGPLOT Procedure to create single bar charts. Now I want to build a chart matrix with several plots using the SAS Graph template. Everything works fine except that I can not replicate some functionality from VBAR statement with the BARCHART Statement.

I want to order a stacked bar chart in a descending order, which means the bars should be ordered from the largest to the smallest, as well as each stacked bar should be ordered by the size of each categorical level.

VBAR provides the “CATEGORYORDER = RESPDESC” option which solves my problem, but the same option is not working with the BARCHART Statement. Does anyone knows a workaround which leads to the same solution?

TSAS

Re: How to replicate functionalities from vbar with barchart

svh — Fri, 30 Jun 2023 14:55:39 GMT

Have you tried using the statement that helps find code for SAS Graph Template that can replicate something SGPLOT does?
https://sasnrd.com/sas-tmplout-option/

Re: How to replicate functionalities from vbar with barchart

DanH_sas — Fri, 30 Jun 2023 18:30:10 GMT

The SGPLOT and SGPANEL procedures do some extra processing to support this feature. There is not a direct option in GTL to do it. To do this GTL, there four key items:

Pre-summarize your data using PROC MEANS or PROC SUMMARY
Sort the data in ascending or descending order using PROC SORT
Use a BARPARM statement to render the bar chart in GTL
On the category axis (either X to Y), specify SORTORDER=DATA in the DISCRETEOPTS

Let me know if you still have issues.

Re: How to replicate functionalities from vbar with barchart

TSAS2 — Tue, 04 Jul 2023 12:15:07 GMT

I solved my issue. I forgot to mention that my dataset contains two columns with data which need so be sorted independently first. @ DanH_sas your suggestion did not work completely for my problem but put me on the right track. Thanks for that! I solved my issue by following your logic with proc sql in advance.