#Tableau Public토론 중인 항목 34개

Hi Narender, had a look at all four. Mostly small things, and the chart types are generally fine.  

Viz 1. Bars are right for comparing rates. Some of the 100% bars (Undefined under No Deposit, and several of the Refundable ones) are probably very few bookings, but they look as important as Online TA. Add the booking count to the tooltip or label (n=12 style), or filter out segments under a minimum. Also City Hotel and Resort Hotel are sorted differently, so it's hard to compare the same segment across the two. Use one fixed order.  

Viz 2. Careful with seasonality here. This dataset covers arrivals from July 2015 to August 2017, so July and August appear three times and every other month only twice. Adding up all years makes the summer peak bigger than it really is. Use one full year (2016) or show average bookings per month per year. The orange bars are labelled "Count of Is Canceled" in the legend, which reads like cancellations, so rename that to Bookings. And for the channel / customer type part of your question, filters only show one at a time. Small multiples, one small chart per channel, would answer "does the pattern differ" much better.  

Viz 3. The title is the same as viz 1, I think it should say country. A diverging palette suggests there is a meaningful middle, so either centre it on the overall cancellation rate (then orange/blue means below/above average) or use a sequential palette. Countries with only a handful of bookings get the strongest colours, same issue as viz 1, so a minimum bookings filter helps. Portugal is by far the biggest origin in this data and probably deserves its own callout. I'd also remove the Latitude/Longitude (generated) and parking space filters, readers won't use them.  

Viz 4. I couldn't tell what each bubble is without hovering, so label them or use shape for the other dimension. Average days on the waiting list is close to zero for most of the bubbles, because most bookings never wait at all. "% of bookings that waited" would show much more. Bubble size for 0.28 to 1.15 special requests is hard to read, and this one is trying to answer four things at once, so I would split it in two.  

Labels: only the highs/lows or the marks you talk about in the text. Tooltips don't look overloaded to me. 

We all start somewhere, and I think this is a good effort at making an interesting and structured dashboard, with your navigation being good, and your main page having a good number of KPIs, so not overloading the user. My points below are mostly based around deciding what the question is that you're trying to answer with each chart, but I think there are a few things wrong with individual elements, that you need to be careful of (especially Top N and the Order of Operations). Below is my (personal opinion) feedback, which you're welcome to ignore, should you so desire, sorry it's long. 

I find trend (line) charts that combine multiple years confusing. Your chart suggests an amazing trajectory of sales, no matter which year(s) you select. It doesn't illustrate that, every January, there is a catastrophic drop in sales (compared to December). In my opinion, your chart doesn't show a trend when you have all years selected, you're comparing "Octobers" (plural) with "Septembers" (and the other months), which is a discrete date comparison and I'd plot as a bar chart. It's only a trend when one year is selected, because then all the months are in sequence, but because you're only showing your users Jan to Dec, you're misleading them into believing that sales just keep going up and up. Your chart omits this line at the end of every year, which feels kind of important:

On your map, you've highlighted that Mongolia has the lowest sales at $£3.1K, but the mark on the map is NULL (no sales), and if I mouse over Papua New Guinea, it has sales of $1.9K, suggesting that after you've labelled the chart you've changed the filters. Make sure any annotations are correct, because they're pretty static

On your Performance per Sub Category chart, I don't know what a red bar and a green bar mean: it's not the size of the bar; if it's the profit margin, you have the number labels displayed as red (which you appear to be using to mean "bad"?), but against green bars (and is a profit margin of 15.3% "bad"? in the industry I'm in we'd bite your hand off for that). Equally, the actual profit from phones and accessories is about the same, so if the message you want to convey is about good versus bad profit margin, I'm not sure this chart makes that point clear. The main message of a chart shouldn't be one of the secondary preattentive attributes of a chart.

If I mouse over, I can deduce that it's the record count, but your user isn't told that anywhere. 

Finally (sorry), on your shipping delay hotspots, you have the same colour meaning multiple different values, becuase you're using a dynamic legend. If you change the year, the dark red means anything between 5 and 7 days, but visually, Pakistan in 2023 (5 days) is as bad as Cambodia in 2025 (7 days), despite Cambodia having 40% longer delays, on average. For this chart, I would use a static range, where anything beyond my target, e.g. 3 days, is red. As it stands, if the business was transformed, and the longest delay was 1 day, that would still be considered "very bad red".

@Shubhangi Jadhav

 you'll want to Pivot your data in the data source tab (1st tab of every workbook). 

Go to the data source tab, select Male/Female columns, then right-click and from the menu of options, select Pivot:

From there, you'll then see Tableau represents the data as Pivot Field Names and Pivot Field Values (you can click into the header and rename these):

Then you can build your view: 

To get the percentage of same, drag another SUM( [Gender Counts] ) as example field.  Then right-click and select Quick Table Calculation, then from sub-menu to that, select Percent of Total.   

Then set the compute by to use Table Across:

You'll then have what you've asked for in your post: 

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

Hi Aren,

I tried to reproduce the issue using the attached workbook in Tableau Public.

I followed the same steps:

• Fertility Rate → Columns

• Life Expectancy → Rows

• Unchecked Aggregate Measures

• Year → Pages

• Population → Size

However, I was unable to reproduce the error. The visualization worked as expected, including the Pages control and Size encoding.

Based on that, the issue may be related to a specific Tableau Public version, workbook setting, or environment rather than the dataset itself.

Hope this helps narrow down the cause.