This is to provide further information to the mapping issue. There is an issue. Replicating the issue in a new report is not straight forward and might not reveal an issue. This issue is mostly afffecting existing maps. This is because in the past, we wre forced to modify location data for Power BI to better parse the locale. In the past, for example, I had to append both State and Country to a County data point for the map to render correctly. When we settled on wht worked, all our configurations were made that way. As fo sometime last week, those same maps stopped rendering all together (ONLY in Power BI Service, not on desktop). Upon further investigating the problem, I found that the map works fine online if I remove the "USA" reference. So the problem seems to be with how the data point is being parsed. Something obviously changed on the service as the issue is being observed by others as well. In addition, my map is configured with a hierarchy of County and then Zip Code. To make matters worse, zipcode data seems not to parse at all. Seems to pick up only one data point. This means I cannot 'Drill-down' from County level to Zip code level.
This is an EXTREMELY URGENT matter. Replicating the issue is not straight-forward but the issue definitely exists.
FYI: This is the second issue I have reported on mapping in less than one month. The first issue was with right-clight reseting the map selection. I have yet to see the fix for that though I was told it is in testing and will be in production soon.