Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Shape map extending from central point

Hi all

 

I have a custom shape map based on UK LSOA boundaries. While the data visualises fine in QGIS, it jumps out from a central point to present a warped map in PowerBI. There is also no visible gradient for the value I'm trying to visualise (LSOA deprivation data).

 

I am using the Equirectangular projection and have tried the others, but they don't work.

 

I downloaded the shape file from the government geoportal and then used MapShaper to convert to topojson. As context, I was able to visualise a similar shape map (also downloaded from the geoportal) using centroids and that worked fine. I have also tried using a clipped version of the LSOA polygon map, in case it was due to the map being too large, but I get a similar results. 

 

Any help would be much appreciated!

Need Help
  • HotChilli's avatar
    HotChilli
    4 years ago

    export it from mapshaper using wgs84.-->  "-proj wgs84"

    You might want to simplify the map first also, so that it doesn't take too long to render in powerbi.

3 Replies

  • HotChilli's avatar
    HotChilli
    Community Champion
    4 years ago

    export it from mapshaper using wgs84.-->  "-proj wgs84"

    You might want to simplify the map first also, so that it doesn't take too long to render in powerbi.

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Thank you! Worked a treat.

     

    The original map was using a OSGB36 projection, so I just converted it to WGS84 when exporting from QGIS. Simplifying it in MapShaper really sped things up too. Much appreciated!

  • Dal_25's avatar
    Dal_25
    New Member
    1 year ago

    I also had this problem, but none of the solutions seemed to work. After looking at the JSON in a text editor, I tried replacing:

     

      "transform": {
        "scale": [
          1.777329117207265,
          1.7654004184142325
        ],
        "translate": [
          170990.34939999972,
          5425574.183800001
        ]
     
    With:

    "transform": {

        "scale": [

          0.000011857228404904743,

          0.000007559092235562255

        ],

        "translate": [

          -110.64553919951076,

          49.98942538559014

        ]

     

    I'm not a GIS person, so I have no idea what this does, but it worked. I hope nobody else has this problem and it was just me, but just in case I thought I'd note it here. I doubt the specific numbers matter, I just had two shape files that worked and compared the ones that didn't to them.