Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
In Power BI, I’ve built a dashboard using the ArcGIS map visual, leveraging fields like Region, Country, Site Code, Latitude (DDY), and Longitude (DDX). Until yesterday, the map was displaying all points accurately. However, today when selecting the "Americas" region and filtering for the USA, some locations—like Virginia—are appearing incorrectly, such as being placed in Australia.
Is anyone else experiencing this issue recently? Any suggestions on how to resolve it?
Solved! Go to Solution.
Hi @vna_7 ,
Thanks for posting in Microsoft Fabric Community.
I tested the behavior using the ArcGIS visual and observed the following:
Using only Latitude and Longitude without placing Site_Code in the Location well resulted in correct placement of the points in Virginia, United States. When only Site_Code was used without coordinates, some points were misplotted, such as Virginia appearing in Australia.
With all three fields :-Latitude, Longitude, and Site_Code used together, the map correctly showed the locations, but a message appeared stating that the data was outside the expected range for the WGS 1984 spatial reference. This indicates that while the coordinates were used, the Location field may still have triggered a geocoding validation warning.
The issue seems related to how ArcGIS interprets the Location field. Values like "Virginia, AUN1" can be ambiguous and may lead to incorrect results when used alone. One way to avoid this is by creating a new column with clearer geographic context, such as "Virginia, United States", and categorizing it as "Place" before using it in the Location well.
Make sure the Latitude and Longitude columns are categorized as "Latitude" and "Longitude" respectively under the column data category in the model view. Using only these two fields for mapping while moving Site_Code to the Tooltip or Legend tends to give consistent and accurate results.
Also, please make sure that the Power BI Desktop is updated to the latest version to rule out any recent regression in the ArcGIS visual.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.
Thank you.
Please find .pbix attached for reference
Hi @vna_7 ,
Thanks for posting in Microsoft Fabric Community.
I tested the behavior using the ArcGIS visual and observed the following:
Using only Latitude and Longitude without placing Site_Code in the Location well resulted in correct placement of the points in Virginia, United States. When only Site_Code was used without coordinates, some points were misplotted, such as Virginia appearing in Australia.
With all three fields :-Latitude, Longitude, and Site_Code used together, the map correctly showed the locations, but a message appeared stating that the data was outside the expected range for the WGS 1984 spatial reference. This indicates that while the coordinates were used, the Location field may still have triggered a geocoding validation warning.
The issue seems related to how ArcGIS interprets the Location field. Values like "Virginia, AUN1" can be ambiguous and may lead to incorrect results when used alone. One way to avoid this is by creating a new column with clearer geographic context, such as "Virginia, United States", and categorizing it as "Place" before using it in the Location well.
Make sure the Latitude and Longitude columns are categorized as "Latitude" and "Longitude" respectively under the column data category in the model view. Using only these two fields for mapping while moving Site_Code to the Tooltip or Legend tends to give consistent and accurate results.
Also, please make sure that the Power BI Desktop is updated to the latest version to rule out any recent regression in the ArcGIS visual.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.
Thank you.
Please find .pbix attached for reference
This worked. Thank you.
I had a Field in Site_code as : Virginia Potential ,which likely caused the issue.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
80 | |
79 | |
59 | |
36 | |
35 |
User | Count |
---|---|
99 | |
57 | |
56 | |
46 | |
40 |