Forum Discussion
Map visualization limits and issues
Seems clunky to have to add yet another column to my data when the tool is supposed to understand and use filters for geo-coding intelligently.
If the new column isn't stored in the DW, then every time end-users who are supposed to use the tool will run into the same problems.
Well, city names are not unique so if you city name is Paris, i would not expect the mapping engine to know which Paris it is. So adding a state to a city name helps with that.
When drill down is back, one thing I would expect to improve would be for the map to remember what state I drilled into so that it can only show the cities in that state without me having to add the state to the city name. Other than that, I think having a field in the model that uniquely identifies a location is probably the safest way to go about it.
What I did is concatenated Address, City, State, Zip and it plots points pretty well. This is good for customer level but you will run into value limits. Question is, what is the official limit?
I can't think of the source but for some reason I recall hearing that it was around 500. Would love to know the official number...
