nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add missing geographic transformation for the UK into ArcGIS Online

Panagiotis

We have been testing ArcGIS Pro 3.5.2 recently in my team, and we discovered an issue with a new geographic transformation, OSGB 1936 to WGS 1984 9, which is not recognised by ArcGIS Online after the June 2025 Update.

As a result, after we publish a hosted feature layer from ArcGIS Pro 3.5.2 to ArcGIS Online, the features for the hosted feature layer are shifted by approximately 10m on a map in ArcGIS Online Map Viewer when a basemap in the WGS 1984 Web Mercator (auxiliary sphere) projection is being used (e.g. ‘Topographic’). However, the features are projected correctly on ArcGIS Online when a basemap in the British National Grid projection is being used (e.g. GB Background).

Please note that with ArcGIS Pro 3.5.2 (similarly to the previous versions), the default map projection for a new map is WGS 1984 Web Mercator (auxiliary sphere) (WKID 102100) and the transformation is None. After you change the default map projection (e.g. by adding a new basemap) to British National Grid (WKID 27700), then a geographic transformation is added to the map, which is by default (in ArcGIS Pro 3.5.2) OSGB 1936 to WGS 1984 9 (WKID 7710), which as explained above is not supported at the moment by ArcGIS Online.

The workaround we are using currently is to change the geographic transformation in ArcGIS Pro 3.5.2 from OSGB 1936 to WGS 1984 9 to WGS 1984 to OSGB 1936 OSTN15 before publishing to ArcGIS Online.

This issue is currently affecting a wider team of circa 80 Creators/Publishers in the UK from disciplines such as Geospatial, Transportation, Environment, Ecology, Landscape, Asset Management, Geotech and so forth, who are publishing content to ArcGIS Online for their projects on a daily basis.

It is crucial for us to get this sorted sooner rather than later, because we understand that it is easy for an ArcGIS Pro 3.5.2 user to miss that step of switching geographic transformations and publish content on ArcGIS Online that will be projected incorrectly on AGOL with any further implications this might have on field work, spatial analysis and mapping.

Find more posts tagged with

Status: Open

Comments

David_Brooks

possibly looks like the BUG fix implementation may have been attempted, but, has caused transformations to fail between 27700 and 3857 when 7710 transformation is used. ive had to go in and manually update the admin endpoint JS to use the v7 transformation
IMPORTANT: November AGOL Update has stripped trans... - Esri Community

gis@stirling

@Panagiotis

Hi Panos,

Ah, ok, got you! 🙂

(If I've got the right Panos, may see you at the ESRI Conference in a couple of weeks)

Jonathan

Panagiotis

Hi @JonathanMcD ,

Thanks for your message.

Our ArcGIS Online organisation is covering both the UK and Ireland, so we can't have a GB basemap as the default one. For our GB projects, we create all our content in 27700 as well (unless specifically required otherwise).

However, we cannot control if ArcGIS Pro 3.5.x users opt for a basemap in 102100 (e.g. Topographic or Imagery) while using data in 27700.

By the way, this geographic transformation issue with ArcGIS Online has now been raised with and recognised by Esri Inc and can be traced under the Bugs & Enhancements page with defect number ENH-000179127. They are planning to get it fixed within one to two release cycles (i.e. Oct 2025 or Feb 2026).

Best,

Panos

gis@stirling

@Panagiotis

Suppose a few questions;

- Why is the data not natively being created using likes of 27700 and left without the need for a transformation?

- Why, for the UK staff, are the GB basemaps not being offered or set as a default? Thus avoiding WGS issues.

I create all our content in 27700 and never feel the need to carry out any transformation, unless we receive data from another source. Our org default maps are set, granted we have access to the OS MM suite of mapping, however, users do have access to the GB maps and are instructed as such.