Skip navigation

I may have mentioned to some of you my dad lives in Wimberley. Fortunately his property is well north of town and on a hilltop, so he was not affected by the disaster along the Blanco River. But our family has visited Wimberley for years and are very familiar with the affected areas. So we are interested in information about what happened.


This is not a Tableau presentation, but nevertheless a good (albeit tragic) example of data telling a story. Readings on the line graphs went vertical suddenly, indicating the wall of water people talked about. It knocked out the flood gauge and they started taking measured rates at some point by the asterisk.


To put things in perspective, the discharge volume chart goes off the scale at 70,000 cubic feet per second. Niagara Falls has a flow rate of about 100,000 cubic feet per second.

Credit to Audit Services for figuring this out. Typically, the Tableau folks tell you not to bother with adding a column for percent of total to your data, since this can be easily created using Quick Table Calculation. This adds a custom calculation from the source measure you can use like any of the other measures. It also allows Tableau to adjust percentages automatically vs. locking in a certain number of rows with fixed percentage values.


Audit Services wanted to create a bar chart which represented volume count along the measure axis, but add as the Mark Label what that count represented for percent of total. We tried different ways of applying the calculated field for percent of total, but could not get it to work.


We went back to their original source table in Excel and added in fixed percent columns. When connected to Excel, this causes Tableau to recognize the percent column as designated measure instead of a calculated field. That made the difference and we were able to use both in the display. Don’t understand why calculated fields vs. a designated percent column in the data would make a difference, but it this case it does.