Forum Discussion
Azure map visual mixing up municipalities
Hi!
I'm creating a filled map with a color ramp showing the values of a variable, for Swedish municipalities. The municipalities are grouped by counties and I marked them as location data trying different alternatives (municipalities as counties, the counties as states, and only the municipalities as counties).
The map then shows the municipality boundaries nicely filled with colors according to the rules I specified.
My problem is that the visual leaves one municiplity all empty, while showing the wrong value (and color) for another one. Interestingly, the municipalities are called "Habo kommun" and "Håbo kommun". Håbo is left empty, while the area for Habo is colored and tooltiped with the Håbo data.
The underlying map itself shows all cities correctly, including those containing swedish letter such as the å.
What do I do? Can I change the configuration of the map data somewhere to allow for å?
3 Replies
- 123abc
Community Champion
It seems like you are experiencing a mapping issue in Azure Maps where it's not correctly recognizing the municipalities with special characters like "å." This could be due to encoding or data configuration issues. Here are some steps you can take to troubleshoot and potentially resolve this problem:
Check Data Sources: Ensure that the data source you are using to create the map has the correct encoding for special characters like "å." Make sure that the names of the municipalities in the data source match the names you are using in your map configuration.
Character Encoding: Verify that the character encoding of your data source and your map configuration is consistent. Unicode (UTF-8) encoding should be used to support special characters.
Data Cleansing: Sometimes, there can be inconsistencies in data where similar-looking characters (e.g., "å" and "a") are treated differently. Ensure that the data in your source is clean and consistent.
Map Configuration: Double-check your map configuration to ensure that you have correctly specified the municipalities with special characters in your map data. Make sure you are using the exact names with special characters in your map configuration.
Language Settings: Check the language and regional settings of your Azure Maps configuration to ensure they are set to Swedish or the appropriate locale. This might affect how special characters are interpreted.
Custom Mapping: If Azure Maps continues to have issues with special characters, you might consider creating a custom mapping or localization file that explicitly defines the correct mappings for municipalities with special characters.
Azure Maps Updates: Check if there are any updates or bug fixes related to special character support in Azure Maps. It's possible that a newer version of Azure Maps may have resolved this issue.
Support: If none of the above solutions work, consider reaching out to Azure Support for assistance. They can provide specific guidance and investigate any potential bugs or issues with Azure Maps.
By following these steps, you should be able to address the issue of municipalities with special characters not displaying correctly in your Azure Map visualizations.
Hi!
Thanks for your reply!
2. How do I check encoding of the dataset in Power BI? The data looks correct when I load and transform it, I read it in from Statistics Sweden.
3.My data is clean. There are also several other municipalities with special characters (also, with the same special character å) that are all displayed correctly. Its only Habo/ Håbo where there's a problem.
4. How do I check or change the map configuration? The only option I find is Geocoding culture but there is no option for a Nordic language.
5. Where do I change language settings for Azure maps?
6. How do I do custom mapping??? I saw that I can enter a reference layer json, but that won't take away the underlying map?
When I filter my data on the Azure map visual and exclude both Habo and Håbo, the map still shows the wrong municipality name in the tooltip (without data and color fill).
So I believe this is really a problem in the underlying map?
