Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
10 years ago

ArcGIS Maps for Power BI (Preview) Discussion

Since we announced ArcGIS Maps for Power BI (Preview), we've been getting a lot of great questions and positive feedback.   Let's use this thread for a discussion of ArcGIS Maps for Power BI, inclu...
General Comment
DuncanP's avatar
DuncanP
Icon for Advocate II rankAdvocate II
9 years ago

Hi scottball, thanks for looking into this. You're really going to get fed up with me though, as I've now started to notice geographical postcode districts that are incorrectly mapped as well.

 

so,

 

TS13 is mapped to BS13

TS15 is mapped to BS15

DN55 is mapped to DE55

DN21 is mapped to BN21

SY13 is mapped to DY13

OX17 is mapped to EX17

SE3 is mapped to SS3

SE9 is mapped to SS9

All the IM districts are mapped to CM districts

 

There are also some minor issues with some of the shape data, for example:

A part of NR21 has split off and ended up inside PE31

There is also a small gap between NW1 and N1

PO22 has been split by BN18

Part of BS22 is inside BS24

Part of NE30 is in NE29

There are quite a few more of the bisected districts, which is understandable given the weird shapes some of them have, so this is probably nit-picking really.

 

I'm really enjoying using this though, and I'm very impressed by the speed of it, so thank you.

 

Best,

 

Duncan

 

 

 

scottball's avatar
scottball
Icon for Helper I rankHelper I
9 years ago

Hey DuncanP - 

 

No worries. I think it's all related (regarding the mismatches). Our underlying service used to give error codes for unmatched addresses, which client applications could filter out or handle differently at their discretion. Now the backend service attempts to find a match no matter what - resulting in some undesireable matches. We're working with the team responsible for this behavior to get it modified, and then we'll update our code in turn. It won't get fixed overnight, but rest assured we're working on it.

 

Regarding the bisected districts and weird shapes you might be seeing - in order to keep the speed high, we are 'generalizing' the shapes - that's to say, we're making the shapes a lot simpler than they really are in order to transmit them across the wires quickly. It's a balancing act - we want them to be simple enough that they are fast, but we don't want them so simple that they lose the ability to represent the thing they're supposed to represent. Please let me know if it's erring too much towards the latter and we can take a look at tweaking it a bit. 

 

I'm really happy to hear that despite some hiccups you're enjoying the visual!