Here's an article that could be helpful if you haven't seen it: http://onlinehelp.tableau.com/current/pro/desktop/en-us/help.htm#maps_geographicroles.html#norecognize
Here's a list of what's supported, and in what version as well: What data does Tableau support for building map views
Hope that helps!
Francesca, 2 really basic questions just to be sure...
1) What version of Tableau Desktop are you using?
2) Does Tableau recognize the field in your data that contains the values for Zip/Postal codes as a geographic field (that is, does it have the little "globe" icon next to it)?
If it does, have you tried right-clicking on the field, selecting Geographic role and validating that Tableau is assigning the right role to it?
First of all, thanks for you interest!
1) I am using Tableau Desktop 10.1
2) Yes, Tableau recognizes the field as a geographic field, but when I display ZipCodes in an area map, the map itself tells me that there are about 180 ZipCodes Unknown. I think that Tableau misses some "shapes" for those 180 ZipCodes.
Is there any workaround?
I'm going to read those arcticles, I'll let you know asap!
I'm not trying to second-guess your approach, but another really basic question: are you 100% certain that all the Zip Code values are accurate for Italy?
When you put the Zip Code field into the view, and Tableau generates the map, do you get an error message in the lower-right corner of the map view (something like "180 unknowns")? If you do, what do you see when you click on that error and try to resolve the unknown values?
If you could take screen shots of the "Resolve Errors" dialog and anything else that might be useful, that would help. Or post a sample workbook with sanitized data.
If the zip codes are valid for Italy, and there are no other issues, I'm stumped. My guess, though, is that Tableau can't determine exactly what to do with a subset of the codes: they may be valid for more than one Country geography, so you need to tell Tableau that they're for Italy explicitly.
OK, doing some digging.
I put both County and State on your map (dropped the fields on the Detail mark). That reduces the unknowns to 75 from 83.
Count has 2 issues: Aosta and Monza-Brianza are not recognized. However, if you click on the drop-down arrow for Monza-Brianza, you will find that Tableau represents it as Monza e Della Brianza. If you select that, then at least that one is recognized. This alone drops the total down to 20!
Now do the same for Aosta - in Tableau's list, it's Valle D'Aosta.
That's it! All your unknowns are gone. Look at the image below: no errors in the lower right corner.
I was hoping it was that simple! Much better than doing this by hand!
If you want, and you are able to do it, you might consider changing your source data to match the names Tableau uses. But if you can't you'll just need to remember to do this matching in the future.
One last note: I created this hierarchy so that it visually reminds me to use ALL levels of detail so I catch those mismatches in the future.
I found it useless because, as you can read in the Title, I need to show every ZipCode area, not every County or whatever.
The problem is Tableau can't draw areas for some zipcodes.
I don't want ZipCodes on tooltip as a detail, I need to see the area of every ZipCode in my excel.
Ok, let's explore how Tableau resolves things in maps.
When you put a field onto the map, Tableau tries to find a match in its database of geographical information. Sometimes, there are conflicting or overlapping answers (e.g., 2 Cities have the same name) - so you have to give Tableau a way to differentiate between them. We do that by adding an additional level of detail to the map - maybe County in this case. Now Tableau has a way to show both cities in 2 different locations because it can tell the difference between them.
In your case, it's a little different: because the State names for Aosta and Monza-Brianza don't match Tableau's internal database names, as far as Tableau is concerned they don't exist. We have to find a way to tell Tableau that they DO in fact exist, but with different names. And the only way to do that is to get that level of detail into the view somehow so that we can resolve the differences in that Edit Locations dialog box.
Kent Marten, how can we help Francesca with this? If we put County and Postal Code on the Detail mark, Tableau only renders County borders, not Postal Code. If we take County OFF the viz, Tableau renders Postal Code boundaries, but with errors for the 2 Counties that don't match Tableau's naming conventions for Italy. I suspect that the only way to resolve this is by changing the names of those 2 Counties in the source data. Is that right?
See attached workbook for details. I created a calculated field that changes the 2 County names to Tableau's values and that fixes the view (2nd tab) but it still only renders at County level, not Postal Code.
ZipCodes Not Recognized.twbx 307.2 KB
Is the primary problem that Tableau does not recognize some of the postal code data that you have? We license Italian postal codes from a commercial vendor and that data is updated in Tableau on an annual basis in most cases. Postal codes change all the as well, so it seems likely that your data is out-of-sync with what Tableau has built-in.
Do you know how recent your data is? We can look at updating ours.
Getting more interesting.
If I look at this page: Postal/ZIP Codes province of Rome - Italy
I can't find 00050 as a valid Rome postal code. This is one of the values that Tableau can't find a match for. Francesca, is this a "special" code or perhaps an obsolete code that was retired at some point? In your data, this corresponds to Passo Oscuro, which also does not appear on that page as a valid location name.