Why do 2 EPSG Codes exist for the same coordinate system?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite
1












I sometimes need to publish data in Gauss-Kruger zone 3 and was wondering why there are now the following EPSG Codes which define this CRS.



  1. 31467 - DHDN / 3-degree Gauss-Kruger zone 3

  2. 31463 - DHDN / 3-degree Gauss zone 3

The Parameters are identical. Then why 2 Codes?










share|improve this question





















  • I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
    – Spacedman
    Sep 28 at 7:00










  • @Spacedman see epsg.io/31463
    – LaughU
    Sep 28 at 7:05














up vote
3
down vote

favorite
1












I sometimes need to publish data in Gauss-Kruger zone 3 and was wondering why there are now the following EPSG Codes which define this CRS.



  1. 31467 - DHDN / 3-degree Gauss-Kruger zone 3

  2. 31463 - DHDN / 3-degree Gauss zone 3

The Parameters are identical. Then why 2 Codes?










share|improve this question





















  • I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
    – Spacedman
    Sep 28 at 7:00










  • @Spacedman see epsg.io/31463
    – LaughU
    Sep 28 at 7:05












up vote
3
down vote

favorite
1









up vote
3
down vote

favorite
1






1





I sometimes need to publish data in Gauss-Kruger zone 3 and was wondering why there are now the following EPSG Codes which define this CRS.



  1. 31467 - DHDN / 3-degree Gauss-Kruger zone 3

  2. 31463 - DHDN / 3-degree Gauss zone 3

The Parameters are identical. Then why 2 Codes?










share|improve this question













I sometimes need to publish data in Gauss-Kruger zone 3 and was wondering why there are now the following EPSG Codes which define this CRS.



  1. 31467 - DHDN / 3-degree Gauss-Kruger zone 3

  2. 31463 - DHDN / 3-degree Gauss zone 3

The Parameters are identical. Then why 2 Codes?







epsg






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 28 at 6:42









Robert Buckley

4,7251148101




4,7251148101











  • I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
    – Spacedman
    Sep 28 at 7:00










  • @Spacedman see epsg.io/31463
    – LaughU
    Sep 28 at 7:05
















  • I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
    – Spacedman
    Sep 28 at 7:00










  • @Spacedman see epsg.io/31463
    – LaughU
    Sep 28 at 7:05















I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
– Spacedman
Sep 28 at 7:00




I cant find EPSG 31463 anywhere. epsg.io/?q=31463 or epsg-registry.org
– Spacedman
Sep 28 at 7:00












@Spacedman see epsg.io/31463
– LaughU
Sep 28 at 7:05




@Spacedman see epsg.io/31463
– LaughU
Sep 28 at 7:05










1 Answer
1






active

oldest

votes

















up vote
8
down vote













EPSG:31463 seems to be deprecated and EPSG:31467 is the correct one.



http://spatialreference.org/ref/epsg/dhdn-3-degree-gauss-zone-3/ is stating:




ProjCRS related to inappropriate coordinate system resulting in incorrect axes and name. Use EPSG:31467 instead.




you can see see this, if you compare the AXIS definitions:



PROJCS["DHDN / 3-degree Gauss zone 3 (deprecated)",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31463"],
AXIS["X",EAST],
AXIS["Y",NORTH]]


with:



PROJCS["DHDN / Gauss-Kruger zone 3",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31467"],
AXIS["Y",EAST],
AXIS["X",NORTH]]





share|improve this answer
















  • 2




    I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
    – Spacedman
    Sep 28 at 7:04







  • 3




    EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
    – user30184
    Sep 28 at 9:23











  • Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
    – mkennedy
    Sep 28 at 18:12










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "79"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f297338%2fwhy-do-2-epsg-codes-exist-for-the-same-coordinate-system%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
8
down vote













EPSG:31463 seems to be deprecated and EPSG:31467 is the correct one.



http://spatialreference.org/ref/epsg/dhdn-3-degree-gauss-zone-3/ is stating:




ProjCRS related to inappropriate coordinate system resulting in incorrect axes and name. Use EPSG:31467 instead.




you can see see this, if you compare the AXIS definitions:



PROJCS["DHDN / 3-degree Gauss zone 3 (deprecated)",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31463"],
AXIS["X",EAST],
AXIS["Y",NORTH]]


with:



PROJCS["DHDN / Gauss-Kruger zone 3",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31467"],
AXIS["Y",EAST],
AXIS["X",NORTH]]





share|improve this answer
















  • 2




    I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
    – Spacedman
    Sep 28 at 7:04







  • 3




    EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
    – user30184
    Sep 28 at 9:23











  • Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
    – mkennedy
    Sep 28 at 18:12














up vote
8
down vote













EPSG:31463 seems to be deprecated and EPSG:31467 is the correct one.



http://spatialreference.org/ref/epsg/dhdn-3-degree-gauss-zone-3/ is stating:




ProjCRS related to inappropriate coordinate system resulting in incorrect axes and name. Use EPSG:31467 instead.




you can see see this, if you compare the AXIS definitions:



PROJCS["DHDN / 3-degree Gauss zone 3 (deprecated)",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31463"],
AXIS["X",EAST],
AXIS["Y",NORTH]]


with:



PROJCS["DHDN / Gauss-Kruger zone 3",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31467"],
AXIS["Y",EAST],
AXIS["X",NORTH]]





share|improve this answer
















  • 2




    I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
    – Spacedman
    Sep 28 at 7:04







  • 3




    EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
    – user30184
    Sep 28 at 9:23











  • Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
    – mkennedy
    Sep 28 at 18:12












up vote
8
down vote










up vote
8
down vote









EPSG:31463 seems to be deprecated and EPSG:31467 is the correct one.



http://spatialreference.org/ref/epsg/dhdn-3-degree-gauss-zone-3/ is stating:




ProjCRS related to inappropriate coordinate system resulting in incorrect axes and name. Use EPSG:31467 instead.




you can see see this, if you compare the AXIS definitions:



PROJCS["DHDN / 3-degree Gauss zone 3 (deprecated)",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31463"],
AXIS["X",EAST],
AXIS["Y",NORTH]]


with:



PROJCS["DHDN / Gauss-Kruger zone 3",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31467"],
AXIS["Y",EAST],
AXIS["X",NORTH]]





share|improve this answer












EPSG:31463 seems to be deprecated and EPSG:31467 is the correct one.



http://spatialreference.org/ref/epsg/dhdn-3-degree-gauss-zone-3/ is stating:




ProjCRS related to inappropriate coordinate system resulting in incorrect axes and name. Use EPSG:31467 instead.




you can see see this, if you compare the AXIS definitions:



PROJCS["DHDN / 3-degree Gauss zone 3 (deprecated)",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31463"],
AXIS["X",EAST],
AXIS["Y",NORTH]]


with:



PROJCS["DHDN / Gauss-Kruger zone 3",
GEOGCS["DHDN",
DATUM["Deutsches_Hauptdreiecksnetz",
SPHEROID["Bessel 1841",6377397.155,299.1528128,
AUTHORITY["EPSG","7004"]],
AUTHORITY["EPSG","6314"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4314"]],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",9],
PARAMETER["scale_factor",1],
PARAMETER["false_easting",3500000],
PARAMETER["false_northing",0],
AUTHORITY["EPSG","31467"],
AXIS["Y",EAST],
AXIS["X",NORTH]]






share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 28 at 7:01









Revo

410212




410212







  • 2




    I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
    – Spacedman
    Sep 28 at 7:04







  • 3




    EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
    – user30184
    Sep 28 at 9:23











  • Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
    – mkennedy
    Sep 28 at 18:12












  • 2




    I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
    – Spacedman
    Sep 28 at 7:04







  • 3




    EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
    – user30184
    Sep 28 at 9:23











  • Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
    – mkennedy
    Sep 28 at 18:12







2




2




I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
– Spacedman
Sep 28 at 7:04





I need to add spatialreference.org to my list of places to look for EPSG codes. Thanks. Although epsg.io hides it under the "deprecated" link.
– Spacedman
Sep 28 at 7:04





3




3




EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
– user30184
Sep 28 at 9:23





EPSG-registry is still the authority and it reports one more version of axis order and labels epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::31467 AXIS["northing (X)",north,ORDER[1]], AXIS["easting (Y)",east,ORDER[2]],
– user30184
Sep 28 at 9:23













Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
– mkennedy
Sep 28 at 18:12




Note on EPSG registry: To look at "deprecated" objects, you have set up a login. It's only used send you notices of new versions.
– mkennedy
Sep 28 at 18:12

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f297338%2fwhy-do-2-epsg-codes-exist-for-the-same-coordinate-system%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?