Azure Maps Does Not Use Geo Hierarchy Correctly

[pdelia]

Azure maps does not appear to be using the properly categorized components of an address when mapping locations on a map. I have setup a sample file with two addresses in Washington and Oregon respectively. For one of them the street address randomly lists in Kansas instead of Oregon, despite clearly having a city, state, and zipcode all in Oregon. For the the other address the city of "Auburn" shows up in Alabama instead of the state of Washington, despite all other values showing up correctly in Washington. Generally Azure is exhibting tons of issues like this on a real dataset, where it seems to be entirely ignoring the context of the geo heirarchy in placing it's locations.

This does not happen in the old map visual, which you can see displays all tiers of the address data in their correct location.

https://drive.google.com/file/d/1OkwPwZr8DQPoJ4m-IokPSQub6Qyt169i/view?usp=sharing 

[Anonymous]

Hi @pdelia ,

Please make sure that all of the following are configured correctly：、

1.Your geographic fields are correctly categorized in Power BI. In Data view, select the desired column, go to the Modeling tab, and set the Data Category to the appropriate geographic category.
2.When entering multiple values into the Location field, you create a geo-hierarchy. This enables hierarchical drill-down features in the map, allowing you to drill down to different levels of location.
3.Your location names or addresses match those recognized by the geocoding service used by Power BI. Using latitude and longitude coordinates instead of location names or addresses can improve accuracy.
4.You are using the latest version of the Azure Maps visual in Power BI.

If you have double-checked the above and the problem persists, please provide us with the version of Power BI Desktop you are using and we will investigate further.

Best regards.
Community Support Team_Caitlyn

[pdelia]

I am using the latest (July 2024) release of Power BI. I linked a .pbix showing the exact issue I am describing with everything configured correctly as best I can tell. It demonstrates the data working correctly in the old Map visual but not working in the Azure Map visual.