Skip to main content
Solved

How to edit the FME TopoJSON output so that it will open correctly in Microsoft Power BI's Shape Map visualisation?


philipwhitten
Contributor
Forum|alt.badge.img+12

I would like to make a custom map for Power BI's Shape Map visualisation: https://docs.microsoft.com/en-us/power-bi/visuals/desktop-shape-map

 

When I make a TopoJSON with FME and open it in Power BI I see a completely filled square (basically the bounding box is filled). When I take the TopoJSON generated by FME and process it using the default paramaters of the online mapshaper tool (https://mapshaper.org/) by exporting as a TopoJSON the mapshaper TopoJSON file open's without a problem in Power BI.

 

When I compare the FME TopoJSON files to the mapshaper TopoJSON file using a text reader the only obvious difference that I see is that the parameters are in a different order, but the scale and transformation parameters are similar. I have attached the files to this message.

 

Any ideas on what I need to do with FME so that the outputted TopoJSON files will open in Power BI?

Best answer by debbiatsafe

Hi @philipwhitten​ ,

Our development team has found that Power BI requires arcs and polygons in TopoJSON to be written in a clockwise manner. There is a parameter that controls orientation of areas in the TopoJSON writer and by default, this is set to counterclockwise. Try setting this parameter to clockwise and see if the file appears as expected in Power BI.

View original
Did this help you find an answer to your question?

2 replies

debbiatsafe
Safer
Forum|alt.badge.img+20
  • Safer
  • Best Answer
  • March 18, 2022

Hi @philipwhitten​ ,

Our development team has found that Power BI requires arcs and polygons in TopoJSON to be written in a clockwise manner. There is a parameter that controls orientation of areas in the TopoJSON writer and by default, this is set to counterclockwise. Try setting this parameter to clockwise and see if the file appears as expected in Power BI.


philipwhitten
Contributor
Forum|alt.badge.img+12
  • Author
  • Contributor
  • March 20, 2022

@debbiatsafe​  absolutelty brillian. Changing the orientation to clockwise resolves the problem. 😀


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings