Forum Discussion
ArcGIS Maps for Power BI (Preview) Discussion
Advocate IIHi 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
Helper IHey 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!
dcrespAdvocate IV
We are really keen on this as a mapping tool within Power BI and think it is alreaydy great and has a lot more potenital. The potential for us as large users for Esri products will be being able to login and use our own mapping hosted securely on the Esri server to be able to add into the Esri Power BI map and then share with external users in a secure way. The other key item that we need is to know if this visual will work with Power BI Embeded. scottball are you able to give us any guide as to when we will be able to get to our secured mapping and share that with others. Also I have not seen an answer about if this will work with PBIE.
Thank you for your assistance and please keep working on this great addition to PBI.
DuncanP dcresp Overnight we updated the map to fix the not loading issue. Please try to load the maps that previously did not work and let me know if you encounter any issues.
dcresp regarding Power BI Embedded, we definitely plan to bring ArcGIS Maps for Power BI to Power BI Embedded, we're working on the architecture for that right now. Regarding using content from ArcGIS servers, we are planning in collaboration with Esri to enable sign-in to ArcGIS Online. In fact, these two items are intertwined from an architecture viewpoint which is why we've not yet enabled ArcGIS Maps for Power BI in Power BI Embedded.
Hi Anonymous, has there been any update on the availability of ArcGIS maps for Power BI Embedded? We've been eagerly anticipating this for quite some time!
- DuncanP
Hi scottball
I totally understand the speed considerations: I've tried plugging actual boundaries into the shapemap visual and it's woefully slow.
I don't know whether it's possible to say that when part of a district ends up completely within another one, it could be subsumed entirely? For example, the NR21 district below:
Could the bit of the shape to the left be ignored entirely? In reality, it's a small bit that sticks out past RAF Scunthorpe:
If it were possible to remove the extra bit rather than raise the detail level to go around it, then the speed wouldn't be compromised.
On another subject, if we choose to represent locations as points rather than boundaries, it's no longer possible to use postcode areas or districts as locations. Is that something that might be implemented at some point, perhaps using the centre of the postcode area or district as the location?
And yes, I am enjoing the visual, it's just what I've been waiting for!
Best,
Duncan
- dcresp
scottball it is great to see that the Australian map is now supporting ABS ASGS geographies. It would be good if it also supported PSMA suburbs which are freely avaliable at https://data.gov.au
Is there a way that the pollygons will display in a more complete shape than what I am currently getting which is faily unusable? The filled maps for other countries seem to work a lot better than this.
- dcresp
Hi scottball As the Australian Burea of Statistics is starting to release the 2016 census data soon will you be updating the Esri visual to also support ASGS 2016 as well as 2011. Hopefully with some more usable pollygons. We love the visual and want to make it part of our Power BI Embeded roll out but need a few things to work a little better and support for Embeded and it will be a great tool.
- scottball
Hi dcresp - the free visual includes demographics from the US only. However, if the Australian Bureau of Statistics (or some other agency / organization) publishes the census data as a publicly shared feature service on ArcGIS, you would have access to them as an ArcGIS reference layer inside the ArcGIS map visual.
Later in the year we plan to provide a way to access Esri global demographic content, so keep an eye out for that as well.
- dcresp
scottball sorry I am refering to the ability to represent areas as boundaries when put into Location and the country is selcted. Then choose that you are looking at Australian SA2 areas. There are two issues with this being that the polygons are so bad they make it unusable in Australia and the ASGS boundaries are for 2011 not 2016 so will not work properly for the upcoming census data.
See my previous post of the issues with the polygons. We are very keen to be able to use this visula for census data as we think it has great potential.
