I can't think how because we do not have access to use Latitude (generated) in calculations.You may be better doing new geocoding for all unless someone else can think of something.
I don't think there is a way to do this all inside Tableau.
One alternative way would be to create a table with all your locations, and the Tableau generated lats and longs and export it to say Excel. Then reconnect to this excel source and use that in a calculation. You'll need to do this export / import whenever you get new locations in your data though so not really a super slick solution.
The four "variables" I most wish T would give us access to are:
And no I can't think of a way to do this either.
Thanks for your answers !
Your suggestion is a good one, Robin, but I don't really want to do that, because it would probably be as much effort to refresh with new places as it would be to use the edit locations option.
I've put in an idea for this:
Please vote for it
The Tableau Geo data is contained in a Firebird (open source relational DB) database located in
ProgramFiles (x86)\Tableau\Tableau 8.0\Local\data ; there are also some convenient Tableau DataSource files in that directory. (Tableau has a native connection driver for Firebird.) You could blend in the Tableau Geo db data as a secondary source with your primary data, and then create a calculated field that switches between the Tableau lat/long versus your lat/long. (On a pain scale, this is easy to do, and I've done it many times.)
Alternatively, you could create a new custom geo source by doing some SQL gymnastics merging Tableau data with your data and then load your new source into Tableau via the standard route for adding new sources. This is also pretty easy, but has more 'baggage'.
Finaly, you could make a copy of the as-installed GEOCODING.fdb daatbase file for safe keeping, then load your data into the original database file. (FlameRobin is a decent Firebird SQL tool.) This has the advantage that you can do this once, and Tableau will be extended permanently to understand your cities. This file can be distributed to all your desktop and / or Server installs. More work with this approach, but it's done once; then again, it involves messing with Tableau "internal" data and may not work over future releases, etc.
Good tips, Frank. I didn't know the geo database was in Local > Data
Oooh the first option of connecting to the db and blending sounds like a good workaround for the time being. I did find those datasources to play around with and find what locations are available, though I get lost quite easily. I'm not sure how to do that though when I publish the workbook on the server. I don't know how to connect to the database that is on the server so that I can refresh the setup. If I cannot refresh it, I'd have to remember to amend the datasource and re-upload when upgrades come out.
Dana, there are a couple of ways to solve the publishing problem:
- Create an extract of the geo db and use that
- Copy the Geo db into some shared file area (accessible via a UNC path) and point to that
Managing the process of re-updating the geo database is definitely the biggest headache of the more involved processes; for that reason I definitely prefer to point to local copies of the native geo db.
That's really cool info Frank. I hadn't thought of finding Tableau's actual data
Nice one Frank
Hmm, I should think of creating a script connecting that dB to ESRI and do some batch geocoding.
Thanks for this advice Frank, I got it working and now our users can select to see cities based on what they have filled in, based on what Tableau thinks or "best of both". I'm using an extract to get the data available when published. Still prefer it if the idea is pushed through, but this is a good enough work around for now.