Forum Discussion

rileywells's avatar
rileywells
Frequent Visitor
1 year ago
Solved

Multiple error generation when using geojson as a reference layer in Azure Maps

I have been trying to use Azure Maps (with the October 2024 version of Power BI) to create a filled map of university enrolments by Statistical Area 4 in Australia, utilising the new "Data-Bound" lay...
Need Help
  • rileywells's avatar
    rileywells
    1 year ago

    FYI the root cause of the problem is that some of the "features" (ie. map regions) in my GeoJSON file had "geometry":null - meaning that they were regions that should not be drawn. While most mapping software can handle this problem, Azure Maps reference layers cannot.

     

    If you find yourself with this problem, you will need to delete any features in your GeoJSON file with the "geometry":null tag (see example below). The Power BI devs have told me that they expect a fix to be shipped in a couple of months (but no promises)

     

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi rileywells 

 

I tested it with simple data and the Azure Maps visual seems to work fine.

Please try the following possible solutions:
1. Ensure that you are using the latest version of Power BI and Azure Maps to avoid known compatibility issues. 

2. Go to Options and Settings, select Options, find the Diagnostics tab and select Bypass Geocode Cache.

3. Try a different file format: some users report that saving the file as .json instead of .geojson solves the problem.

 

Here is a similar solved case for reference:
Solved: Azure Maps GeoJSON Reference Layer Stopped Working - Microsoft Fabric Community

 

If the problem persists, please share your pbix file (remove private information).

 

 

Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

  • rileywells's avatar
    rileywells
    Frequent Visitor
    1 year ago

    Hi Jarvis,

     

    Thanks so much for your response. Unfortunately, your sample pbix also causes the afformentioned errors on my PC.

     

    So I think it is something to do with my version of Power BI and not the shapefiles themselves. 

     

    I tried your solutions:

    1. Update PBI and Azure maps.

    Power BI Desktop is updated to "October 2024" (Version: 2.137.952.0 64-bit (October 2024)). I don't know how to check the version of Azure Maps - do I need to update it seperately to PBI Desktop? If so, how?

     

    2. Bypass Geocode cache

    This has no affect and issues are generated in the same way

     

    3. Use JSON instead of GEOJSON

    This also has no affect and causes the multiple errors as before.

     

    I have uploaded the original pbix file I am working on (although I am sure it will work for you, as your state example did), which still throws errors for me. You can access via OneDrive here.

     

    Thanks,

    Riley

    • Anonymous's avatar
      Anonymous
      Not applicable
      1 year ago

      Hi rileywells 

       

      I can't access this OneDrive link, if you don't mind please upload your pbix file directly on the post.

      Regarding the Azure Maps visual update, when you create an Azure Maps visual in Power BI Desktop, if it is old, the following dialog box will be displayed prompting for an update:

       

      Best Regards,
      Jarvis Tang
      If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.