Forum Discussion
ArcGIS Maps for Power BI (Preview) Discussion
Advocate IVscottball any update on when the Australian ASGS boundaries are going to get looked at. Also any idea on when the visual will be avaliable in Power BI Embeded. We want to use the Esri Visual and Power BI Embeded for a 2016 Census data project in July but these two issues are major obsticals at this stage. Thanks
Helper Idcresp - I'm working with our content team to see what we can do regarding ASGS boundary data. To give some background, we have data content providers that provide some of our content (including the ASGS boundaries). The data provider that gives us the ASGS info (along with other boundary data as well) provides annual updates to Esri and due to the publish date of the ASGS data, it will not be a part of the 2016 data update. At this point we will not receive the updated ASGS data until our 2017 data update. I'm pushing internally to see what we can do to get more timely updates, or incorporate content 'off cycle'.
- dcresp
scottball thank you for the update. Waiting till 2017 would certainly be a major issue for us. Your data provider has done a horrible job of normalising the ASGS boundaries to an extent that they are not usable (see my previous picture). If it helps we have a full GIS team using Esri I can get them to provide the ASGS polygons in what ever format you want at no cost. The base information comes from the ABS at no cost in an Esri format. We can re-format this if this would help. The new Power BI Premium means that we can now use the Esri app in external user content instead of using PBI Embeded but we really need to have access to working ASGS boundaries for the census data release in July. Please let me know if there is anything we can do to assist with this.
- mike_honey
Memorable Member
scottball - I second the sentiments ofdcresp , although I dont have any active project for ArcGIS maps. That ASGS boundary issue emphatically killed the ArcGIS visual as a serious contender for all the mapping projects I've been working on.
Fortunately thanks to dcresp sharing his findings on the issue, (I think) I was able to avoid any of my clients actually seeing it in all it's horror. The lengthy delays you describe in accessing freely available data only add to my concerns.
I suggest you should be looking for a new data provider. Do you really want to be reliant on an organisation that:
a) is happy to provide Microsoft and it's customers with data of such poor quality, presumably untested
b) takes so long to fix such an obvious issue, where complete & accurate data is freely available
