Forum Discussion
Multiple error generation when using geojson as a reference layer in Azure Maps
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)
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."
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)