[Proj] towgs84 values for EPSG:27700

Mikael Rittri Mikael.Rittri at carmenta.com
Mon Feb 20 04:45:03 EST 2012

> Is this expected behaviour?

I can say that I, for one, didn't expect it. Because as far as I know,
the default datum shifts in both Proj.4 and GDAL/OGR come from the
gcs.csv file that is part of libgeotiff. 

However, the gcs.csv file is changed now and then. The default datum
shift of OSGB 1936 was changed from the 7-parameter (epsg:1314) to the
3-parameter (epsg:1195) in the libgeotiff changeset 2023, of May 23, 2011.
The changeset message was just "upgrade to EPSG 7.6 database".


(And I just happened to notice that in the same changeset, the default
 datum shift for Qornoq 1927 was changed from the 7-parameter epsg:1798,
 accuracy 1 m, to the 3-parameter epsg:1797, accuracy 48 m.)

I don't know in what libgeotiff release this changeset was (or will be)
included. But it seems that when you used GDAL/OGR from trunk, this changeset was included, whereas when you used Proj version 4.7.1,
it wasn't.

See also Frank's blog: 



Best regards,

Mikael Rittri

-----Original Message-----
From: proj-bounces at lists.maptools.org [mailto:proj-bounces at lists.maptools.org] On Behalf Of Hermann Peifer
Sent: Monday, February 20, 2012 6:56 AM
To: PROJ.4 and general Projections Discussions
Subject: Re: [Proj] towgs84 values for EPSG:27700

On 19/02/2012 21:06, support.mn at elisanet.fi wrote:
> So the reason for the difference is that the OSGB36
> datum is not any standard value.

I am aware that there always might be many values for a single EPSG 
code. I also don't want to debate in how far the values of the "ETRS89 
(WGS84) to OSGB36/ODN Helmert transformation", on p. 33 of [1], can be 
considered as "standard values". My simple (slightly rephrased) question 

ogr2ogr -s_srs epsg:27700 # expands to something
cs2cs -v +init=epsg:27700 # expands to something else

Is this expected behaviour?



Proj mailing list
Proj at lists.maptools.org

More information about the Proj mailing list