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

[rileywells]

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" layer option to use sum of enrolments as a legend. Here is the process I have been using:

1. Go to https://www.abs.gov.au/statistics/standards/australian-statistical-geography-standard-asgs-edition-3... and download the "Statistical Areas 4 - 2021 - Shapefile".

2. Upload this zip file to mapshaper.org, type proj wgs84 in the console (as suggested by the answer on this post), simplify the map to 1%, and export as a GeoJSON file. 

3. Verify that the file looks correct using geojson.io

4. Import the downloaded .json file as a reference layer to Azure Maps.

When I do this last step, several generic error messages are generated (see below), however the boundaries do load. The detailed content of the error messages are very similar to this person's question. Once those errors are closed, whenever the map is moved or interacted with, more errors are generated. Moreover, when adding a field from a table into the "location" field of the Azure maps visual, and trying to use the enrolments measure column to vary the colour of the map, none of the coloured areas change. 

I've uploaded a link to the .pbix file I am working on here: https://drive.google.com/file/d/1SXsw37Vuf0ItHuUyOzfC2oirEPIUBpeh/view?usp=sharing

[rileywells]

For those who may be also facing this problem, I have submitted a ticket to Microsoft, and they believe that it is something to do with the shapefiles I downloaded:

"The root cause of the problem lies in the GeoJSON file containing feature objects without "geometry" properties, which is leading to a null reference issue.

Our Product Group (PG) is actively working on a fix to resolve this. However, at this moment, we don't have an ETA for when the fix will be available."

[rileywells · Accepted solution]

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]

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]

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]

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.

[rileywells]

Hi Jarvis,

I don't get that error message, so I suppose Azure Maps is up to date.

Unfortunately, I don't have the option to upload a pbix file directly to a post - hopefully this google drive link will work: https://drive.google.com/file/d/1SXsw37Vuf0ItHuUyOzfC2oirEPIUBpeh/view?usp=sharing

[Anonymous]

Hi @rileywells 

It does work well on my side as you think.

I'm having a hard time finding the cause of the problem due to not being able to reproduce this problem.

It is recommended that you open a ticket and a dedicated Microsoft engineer will resolve the problem for you, this will be free if you are Pro account.

How to create a support ticket in Power BI - Microsoft Fabric Community

Thank you for your understanding.

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]

Thanks Jarvis,

I will submit a ticket as you've suggested - thanks for all your help.

[rileywells]

Hi @rajendraongole1 ,

Even reducing the complexity of the model way down to 0.1% (which gives a woefully simple map) still causes the error. The file is only 66 KB.

And the GeoJSON validator you suggested verifies any GeoJSON file I give it as correct.

[Roman_Zalesskii]

That is because your geojson file is too big. I tried several versions with different file sizes and the biggest always gives me error. Use this service to simplify shapes in your geojson - https://mapshaper.org/

[rajendraongole1]

Hi @rileywells - Simplifying the GeoJSON file might help, but it's possible the file is still too large or complex. When simplifying, you might want to reduce it even further (to less than 1%) to ensure it works smoothly in Power BI. Sometimes complex shapes or large files can cause rendering issues in Azure Maps.GeoJSON Format: Ensure the GeoJSON format is valid. Since the boundaries load initially but fail when interacted with, the GeoJSON file may have some errors or unsupported features. Double-check the file for any unnecessary properties or geometries that Power BI might struggle to handle. You can validate the GeoJSON using tools likeGeoJSON Viewer & Validator (geojsonlint.com)

It's worth noting that the Azure Maps visual is relatively new and may have some limitations, especially when dealing with custom GeoJSON layers. Ensure that Power BI and Azure Maps are fully updated to the latest versions to avoid bugs that might have been fixed in later patches.