3 of 3 people found this helpful
With a Map view Tableau has a restriction
of only one pair of Lat/Long fields per view --
whether it's a simple map or a dual-axis one.
So even if there are several Lat/Long pairs per datasource,
one could not use more than one pair per view, period.
To use values from a two (or more) Lat/Lon pairs,
one should combine them into a single Lat/Lon pair anyway.
It could be per datasource -- by UNIONing tables
on a common fields (including Lat/Long ones) --
typically via SQL.
Or it could be per view -- and an approach is to choose
from the proper Lat/Lon pair depending on a view granularity.
For example, if there is a Mark per distinct City, then Lat/Lon pair
corresponded to a City should be taken into a calculated Lat/Lon for a view.
Please find the attached wb with examples
of the original view -- with Lat/Lon (generated) --
and a couple of seemingly "identical" views made with
Lat/Lon pairs calculated from several others available in the DS.
Please find also an excel file used as Primary datasource(s)
for both views (Sheet 7a -- "straight" DS, Sheet 7b -- using Pivot).
For simplicity let's States to be your Vendors
and Cities to be your Customers.
Hope this could help.
Thanks for clearing that up! I ended up combining columns outside of Tableau.
Could you please mark the above answer which helps you as Correct Answer.
It will help others.
The topic is rather old, and it's a chance for it to become outdated.
BTW, starting from the version 2018.1 it is possible to combine
the Tableau-generated and custom Lat/Lon fields on a dual-axis view:
Yeah its interesting and looks good and flexible.
Thanks for the reference.