There are many predefined transformations available in ArcGIS to transform between OSGB36 and WGS84. These range from very accurate (+/- 2m) to relatively inaccurate (+/- 35m), depending on where you are.
NOTE: If you do not select a transformation, ArcGIS will still transform the data but not do a datum shift with a resulting accuracy of over 100m.
A complete list of transformations available in ArcGIS and their accuracies is available on the Esri Resource Centre.
Usually the recommended transformation to use that is built into ArcGIS is the OSGB_1936_To_WGS_1984_Petroleum one (this uses the same parameters as the 7 parameter shift recommended by Ordnance Survey). This has an accuracy of +/- 5m.
However, if a more accurate transformation is required, the Ordnance Survey OSTN02 transformation should be used.
By default ArcGIS does not contain the OSTN02 transformation from Ordnance Survey that should be used to convert data from OSGB36 to WGS84 for the highest accuracy; however in ArcGIS 10.x it is simple to implement (note you only need to do this once):
a) Download the grid shift file from Ordnance Survey: OSTN02 data file
b) Extract and copy the file OSTN02_NTv2.gsb to the folder:
“C:\Program Files (x86)\ArcGIS\Desktop10.2\pedata\ntv2\uk “ (or equivalent installation folder, e.g. replace 10.8 for 10.2 if you are running 10.8)
c) Note you will need to create the ‘uk’ (lowercase) folder as a subfolder of ntv2.
d) On reloading ArcGIS (or just reopening the Trransformations dialog) you will notice a transformation available if you choose OSGB36 to WGS84 called OSGB_1936_To_WGS_1984_7 that is using the OSTN_02 method.
If you don’t use the OSTN02 method you should use the OSGB_1936_To_WGS_1984_Petroleum transformation. You should always explicitly choose a transformation and never accept the default!
We use cookies for security purposes, remembering your preferences and to analyse site traffic in order
to improve your experience using the service. This includes anonymised Google Analytics data.
We won't share your data with anyone else.
For more information please see our
Cookie Policy page.