Coordinate System Issue with Layers Hosted on ArcGIS Online after Recent Update

[EmmettHurley]

Hello,

I am experiencing an issue with certain hosted layers on AGOL -  and it appears to be a coordinate reference issue, specifically with layers in the British National Grid (BNG) and WGS 1984 Web Mercator (WM).

I have noticed that the issue began following the 14th of June update to ArcGIS Online. Layers, that for years had projected correctly, were now showing in the Gulf of Guniea off the west coast of Africa.

I conducted several tests and found the following with the latest update:

• When sharing a web layer from a ArcGIS Pro project in the BNG coordinate system:

  • The layer will appear in the Gulf of Guniea (both BNG and WGS84 MW layers)

• When sharing a web layer from a ArcGIS Pro project in WGS 84 WM coordinate system:

  • BNG layer is displayed about in the right area but slight projection issues.
  • WGS 84 WM layer is displayed in the correct location.

It seems that the hosted layers are displayed correctly only if both the layer and the ArcGIS Pro project are in the WGS 84 WM coordinate system. However, this is not an ideal solution for me, as my data mainly used within the UK and the BNG system provides the most accurate measurements for my purposes. These layers have projected correctly for years.

I would like to understand why this issue has occurred after the recent ArcGIS Online update, and if there is a way to resolve it without having to convert all my layers to the WGS 84 WM system and re-hosting. Any insights, advice, or experiences shared would be highly appreciated.

Thank you.

[Richard_Purkis]

@EmanueleGreco_GNetwork @EmmettHurley

 I have just come across this recommendation for any customers still experiencing issues after the BNG bug last week, please rebuild the Spatial Index. More information here

• Rebuild the spatial index

Hope this helps

[Richard_Purkis · Accepted solution]

Hi @EmmettHurley 

Just to reply to this thread for wider awareness, this was logged as BUG-000159105 and was fixed overnight. 

Thanks for raising it the first place. We saw a lot of cases raised and that helped Esri realise this was a major issue and helped isolate the cause of the issue quickly.

If you see any more issue isses please raise them as a new post

Thanks

[EmmettHurley]

Okay @Richard_Purkis  thanks. I will raise a new post then as while the projection bug is fixed the performance of those layers is terrible. They're incredibly slow to render and brings down the performance of the app in general.