Well you got my attention with the title - now you just need to provide a packaged workbook (*.twbx). (The *.twb file doesn't include the data.) I'm sure someone will be able to answer your question once you've uploaded that.
Hi Richard - Thanks for replying... I've attached it as a packaged workbook.
Now I've unchecked the "aggregate measures" option and the points in my example are laid out in one line, again nowhere close to where they should be.
I'm using lat and long from the data, not the generated versions. I've got both set as continuous dimensions.
Could it be a data type issue or something wrong with my underlying spreadsheet? I'll attach that as well.
In the underlying spreadsheet I"ve got the lat, long values formatted as Unicode with a leading ' (single quote).
1 of 1 people found this helpful
You just had your latitude and longitude swapped - so the values which are really longitude were being treated as latitude - and latitude of -122 is south of the south pole. ;-)
Wow... I knew it had to be, um, *subtle*. :-)
Almost out of the woods here. After seeing that your file works, I replaced that data with a more representative sample. Now I've got all the points laid out correctly but, for some reason, the background map doesn't render anymore.
In fact, at no point does Tableau go into map mode. Lat and Long are selected as such in Geographic Role. Here's my order of operations:
1. blank sheet.
2. drag latitude pill to column shelf, set to dimension, continuous
3. drag longitude pill to column shelf, set to dimension, continuous
4. set level of detail (geoID), label, and size.
5. remove the "show headers" option so the axes go away.
Again, many thanks in advance for any feedback.
You still have the latitude and longitude swapped. The column that you have labelled as [stop_lat] is really a longitude and vice-versa.
Last time I just changed the geographic roles over but left the field names the same. This time I've created calculated fields to try to make it clearer what is happening.
When Tableau recognises proper latitude and longitude you don't have to do anything to hide the axes - that just happens automagically.
I'm basically speechless. No wonder I couldn't even figure out an appropriate search query for this problem.
I just always assume that coordinates are given, Lat first, Long second. The Google Maps API is LatLng. So, when I grabbed my source data and extracted the text, I failed to notice that it was actually reversed to Long, Lat.
Is this generally wrong? Think I should let them know? Nope... http://en.wikipedia.org/wiki/Keyhole_Markup_Language#Geodetic_reference_systems_in_KML
Thanks a million. Tomorrow I might actually make progress.