Tuesday, November 29, 2011
I've been meaning to create a tax adjustment calculator. I started with the 2009 IRS summary data here and then created a "change the tax rate" scenario.
As I type this, I remain firmly neutral to this issue. However, it is interesting to note that even the smallest changes in tax percentage points add up to significant overall changes. Ask yourself: what can 1 billion dollars provide if handled properly by the US government? How about a 100 billion?
Download the workbook to pick away at it, change it, improve it, or scoff at it. It is by no means perfect. Just an idea that I wanted to mess around with. The last tab contains more references. Each tab has a quick comment on what's going on.
Wednesday, November 16, 2011
Monday, November 7, 2011
Friday, November 4, 2011
In the example below, I placed gradient reference lines for 95,90,86,83,81,80, and 75% (and their counterparts). You can adjust the occupation slider to update the visual.
Wikipedia is a good place to start on this chart type.
Friday, August 26, 2011
Thursday, August 25, 2011
As a follow up to my previous post on Bollinger Bands, I took a stab at MACD, which derives from similar calculations.
This is a somewhat squirrely subject and I might be opening myself up to attack or a can of worms in this attempted analysis. As a preemptive strike against such attacks, let me start off by saying that as a stock trader, I fall firmly in the "fundamentals" camp, and this type of technical analysis does little for me. Second, allow me to graciously further admit that my math could very well be wrong. Finally, grant me the chance to comment on the fact that we can find on the internet dozens and dozens of permutations on the mathematics of this MACD subject.
Three web links which I found quite helpful in understanding the math behind MACD are these:
The Wikipedia Page on MACD
The Wikipedia Page on Moving Averages and Exponential Moving Averages
which are required components of MACD analysis, and lastly,
A Stock Charts Dot Com web page which has a nice discussion on the subject.
Feedback on the mathematics is welcome.
Wednesday, August 24, 2011
1. Start with a moving average - the industry standard appears to be "20 trailing periods".
2. Create a upper band from this average which is 2*STDEV(same periods) + moving average
3. Create a lower band which is moving average - 2*STDEV(same periods)
However, I have added Tableau Parameters because there are several variations on the Bollinger definition. E.G. instead of using a multiplier of "2" you can vary this, and instead of defining the moving average as "20 periods" can you can vary this. Download the book to review the calcs - it's remarkably simple, thanks to Table Calcs. Enjoy!
Friday, August 19, 2011
Thursday, August 4, 2011
A quick post for "what's new in 6.1" specific to mapping: Dark Maps, Built-in Geocoding for Cities worldwide, and cartographic labels in French and German. These are three great features that make the mapping sizzle even more than before!
For the full list of 6.1 features, see the release page
Geocoding for Worldwide Cities
Cartography Labels in German and French
Friday, June 3, 2011
Tuesday, May 31, 2011
The website to get started is http://www.ars.usda.gov/services/docs.htm?docid=8964.
Tuesday, April 19, 2011
In short: Google provides a thorough API for querying Google spreadsheets. This syntax can be triggered by a Tableau "URL Action". You are going to need to download this workbook and reverse engineer the google API and URL syntax, because as I have repeatedly said before, I am quite lazy sometimes...
Tuesday, April 5, 2011
An ongoing project of mine will be to slowly amass this information into one unified view. This will exceed the capacity of Tableau Public, of course.
Anyway, the first step was to convert the FIPS codes as represented in shapefile format, to a valid polygon format that Tableau can understand. (This subject has been covered elsewhere in this blog as well as on the web). Notes: I provided Tableau with a copy of this polygon file, and you can download it here. FIPS code = US Counties. The Census download website is here. The income and poverty excel file is here. And the master key excel file is here.
Tuesday, March 29, 2011
I find some of these techniques to be annoying - too much tabbing and too much "I need to know how to navigate a priori" - perhaps I am just complaining. It's not that hard I guess. Also, this viz breaks my rule about creating small vizes in 2011 (the goal was to print a letter portrait dashboard however) Anyhoo, a work in progress.
Friday, March 25, 2011
On the first viz shown below, we calculate the quadrants of the latitudes and longitudes in order to provide geographic 'slicing' filters. On the second viz shown below, we also created percentile calculations to provide additional filters based upon the individual latitudes and longitudes - essentially, this creates the effect of providing axis range sliders.
The only requirement here is that your latitudes and longitudes must A) exist as actual fields (as opposed to using Tableau's built-in geocoding) and B), must be aggregate, e.g. AVG(latitude or longitude). Thus, your level of detail will affect the construction of this example.
Hopefully I won't get in trouble for stealing the outer limits logo. I mean, geesh, it's almost fifty years old at this point.
Thursday, March 24, 2011
Tuesday, March 22, 2011
Because each Table Calculation can have its own "scope" or "partition" this turns out to be pretty easy to create. Enjoy!
Thursday, March 3, 2011
The net result is the effect of "show me" or chart selection, for a given data set. There are some inherent weaknesses to this approach, but overall it's pretty nifty.
Tuesday, February 15, 2011
Thus did they gather around the warm fires of the viz furnace, hammered away they did on the anvils of analysis - and when they were done, Lo, Verily, they put this book together to answer that question. Team Geiger rides again in 2011.
Monday, February 14, 2011
UPDATE: Some folks asked for more details on how this is achieved. I have tried to write it up a bit more. The details are below the visual. I really don't know why this is such a tedious process... but it is. Hopefully my additional notes below will help.
There are a few different ways to get a shapefile into Tableau as "polygon" data.
Joe Mako has a great video located here:
The "shp2text to ms access to tableau" method. Download all three of these files to a directory:
Download shp2text.exe from here:
from a prompt, run this command:
shp2text.exe --spreadsheet 55mu500gc.sph > output.tab
This outputs the contents to a tab delimited file called "output.tab"
Now import this file into MS ACCESS - when importing, tell MS ACCESS to add a "primary key" - you will use this new column in Tableau for the Tableau "path ID". Also, during the import, make sure that you tell MS ACCESS that "the first row contains field names".
Once the data is inside of MS ACCESS, you can now connect to it with Tableau, and follow the general instructions for polygons found here:
If you have ArcGIS, you can follow these instructions instead, as they will save you some time:
Field Names of importance, specific to the Brazilian data set:
X-Coordinate: this is the longitude, set this to "longitude" in Tableau
Y-Coordinate: this is the latitude, set this to "latitude" in Tableau
ID2: this is the MS Access generated primary key, you will want to use this on the "path" shelf in Tableau.