Forum Discussion
more location data required?
Ever since the Launch, I had a map that worked using zipcode now, the same chart gives me the following error:
To create a filled map, the Location data should include Bing Map-supported geographic data, such as country/region, state/province, or postal code.
I am using postal code - rather US zip code.
Any thought or is there a known bug? It worked okay in the preview (I say okay only because it never kept my "zoom" and I'm only looking at places in California, so my filter on zipcodes is California)
12 Replies
So I figured out the issue, apparently the field literally has to say Zipcode. Before it worked with a business logical named of Job Zip (referring to the zipcode of the vendor job for my data) But when I fixed my cube's dimension attribute to zipcode and works great now.
I know that makes perfect sense but why did it work with a different name in the preview and then get so specific in the release? Seems like a step backwards.
It had nothing to do with the model or granularity, it had to do with the fact it worked in Preview but when they did the release they got specific. So unless you specifically labeled the Dimension attribute, or table attribute, Zipcode instead of say "Zip City" it wouldn't work. That is a big miss. Maybe my business unit doesn't want it called Zipcode or Postal Code. Maybe they want it Zip City. So to me, that's a fail because a true Dimension model (ala Kimball) is based on Business Process and what the business calls it, not what the application wants it to be.
I have a similar issue however power bi will plot some but not all of my zipcodes. For example it will work fine in California, but not plot an zipcodes in Illinois. Any idea as to why it will not plot certain zipcodes?
I tried naming my fields [Postal Code] and the American name of [Zip Code] but no cigar. I even tried a concatenation of City, Postal Code and Country in one field but again no luck. The only way I could get this to work was to concatenate the latitude and longitude together in a string with a comma separating the two.
Note that I my data is in Excel tables and not a cube. In SSAS at least you can define an attribute with a Geography type, but I doubt this will work.
skiwii - Coming in late to this conversation, but it seems like the trick that is missing is Data Categorization. I created a Enter Data query with some zip codes, doesn't matter what the column is called, mine was called Zips.
In the model, change the data categorization to "Postal Code". If you had Country, you would categorize it as "Country", etc.
Place the categorized fields in the Location area. See below:
skiwii you can now define Data Category in Power BI desktop much like you could in SSAS, so you can click on a field with Zip data and Categorize it as a Postal Code.
Now, for some reason, it seems like there is some sort of an issue happening from the geocoding perspective, i noticed that my states and cities are geocoded fine today, but states are fluky, so I am wondering if there is a bug in a service with geocoding zipcodes right now
