Skip to main content
7 件の回答
  1. 2014年2月3日 21:51

    HI Matthew,

     

    The polygon/dual axis was all Tableau.

     

    Not how I would have done it, but it doesn't mean to say it can't be done.

     

    The "trick" with polygons and points is the same for any Tableau mapping:

     

    Remember Joe Mako's advice: Tableau mapping is just a scatterplot.

     

    With that in mind, you need to think about what you're analysing: I always recommend analysing at the lowest level of detail: in this case, it wasn't schools, it was students (i.e. who is going to be affected by proposed changes).

     

    So to do a dual-axis (i.e. areas, which are joined up dots in a specific order) + dots of the unit of analysis: (how? on the school they attend? = left outer join on school).

     

    So your dataset needs every point of the polygon (i.e. the area of the school boundary), with the features (i.e. the school name) + all the points you want to plot for the pupils.

     

    The reason I don't advocate this is that it makes the datasets huge, slow to render etc.

     

    Much better making shapefiles (that don't change much over time): in this case, current and proposed.  Layer them with your background map layer, and then present those via Geoserver/WMS to Tableau, and then concentrate on the foreground analysis.  If you need to calculate how many objects are in a certain area, then it's a matter of a calculated field over the join; you don't need to "show" that in the view; a simple bar chart would do just fine.

     

    Here's a blog post for those that haven't read it.