QGIS EPSG value differs from ArcGIS and spatialreference.org











up vote
1
down vote

favorite












Background:



I have both QGIS 3.4.1 and ArcGIS Desktop 10.6.1 installed on the same laptop, Windows 10.



I have a polygon shapefile that is projected to Lambert Conformal Conic. Arc states that the shapefile's EPSG value is 102004. Here's a screenshot from the Arc Layer Properties:



enter image description here



spatialreference.org agrees with Arc; 102004 is Lambert Conformal Conic:



enter image description here



So far, so good!



Problem:



QGIS states that this layer's EPSG value is different: 100027. Here's a QGIS screenshot:



enter image description here



But wait, there's more! spatialreference.org does not have an entry for 100027. Here's a screenshot:



enter image description here



Question:



Why doesn't the QGIS EPSG value match Arc and spatialreference.org? What does the 100027 value represent?










share|improve this question
























  • 102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
    – Luke
    1 hour ago










  • QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
    – user30184
    1 hour ago

















up vote
1
down vote

favorite












Background:



I have both QGIS 3.4.1 and ArcGIS Desktop 10.6.1 installed on the same laptop, Windows 10.



I have a polygon shapefile that is projected to Lambert Conformal Conic. Arc states that the shapefile's EPSG value is 102004. Here's a screenshot from the Arc Layer Properties:



enter image description here



spatialreference.org agrees with Arc; 102004 is Lambert Conformal Conic:



enter image description here



So far, so good!



Problem:



QGIS states that this layer's EPSG value is different: 100027. Here's a QGIS screenshot:



enter image description here



But wait, there's more! spatialreference.org does not have an entry for 100027. Here's a screenshot:



enter image description here



Question:



Why doesn't the QGIS EPSG value match Arc and spatialreference.org? What does the 100027 value represent?










share|improve this question
























  • 102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
    – Luke
    1 hour ago










  • QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
    – user30184
    1 hour ago















up vote
1
down vote

favorite









up vote
1
down vote

favorite











Background:



I have both QGIS 3.4.1 and ArcGIS Desktop 10.6.1 installed on the same laptop, Windows 10.



I have a polygon shapefile that is projected to Lambert Conformal Conic. Arc states that the shapefile's EPSG value is 102004. Here's a screenshot from the Arc Layer Properties:



enter image description here



spatialreference.org agrees with Arc; 102004 is Lambert Conformal Conic:



enter image description here



So far, so good!



Problem:



QGIS states that this layer's EPSG value is different: 100027. Here's a QGIS screenshot:



enter image description here



But wait, there's more! spatialreference.org does not have an entry for 100027. Here's a screenshot:



enter image description here



Question:



Why doesn't the QGIS EPSG value match Arc and spatialreference.org? What does the 100027 value represent?










share|improve this question















Background:



I have both QGIS 3.4.1 and ArcGIS Desktop 10.6.1 installed on the same laptop, Windows 10.



I have a polygon shapefile that is projected to Lambert Conformal Conic. Arc states that the shapefile's EPSG value is 102004. Here's a screenshot from the Arc Layer Properties:



enter image description here



spatialreference.org agrees with Arc; 102004 is Lambert Conformal Conic:



enter image description here



So far, so good!



Problem:



QGIS states that this layer's EPSG value is different: 100027. Here's a QGIS screenshot:



enter image description here



But wait, there's more! spatialreference.org does not have an entry for 100027. Here's a screenshot:



enter image description here



Question:



Why doesn't the QGIS EPSG value match Arc and spatialreference.org? What does the 100027 value represent?







qgis arcgis-desktop coordinate-system epsg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









Vince

14.3k32646




14.3k32646










asked 1 hour ago









Stu Smith

1,8381330




1,8381330












  • 102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
    – Luke
    1 hour ago










  • QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
    – user30184
    1 hour ago




















  • 102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
    – Luke
    1 hour ago










  • QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
    – user30184
    1 hour ago


















102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
– Luke
1 hour ago




102004 isn't an EPSG code, notice it is ESRI:102004 not EPSG:102004 in spatialreference.org and WKID:102004 Authority:Esri in the layer properties.
– Luke
1 hour ago












QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
– user30184
1 hour ago






QGIS does not state that it is an EPSG code. QGIS considers that CRS as somethign that does not belong to the EPSG database and gives it some number that is not reserved for EPSG codes. You can see that all the parameters are the same which means that this CRS behaves in the same way even it has a different code in QGIS.
– user30184
1 hour ago












1 Answer
1






active

oldest

votes

















up vote
2
down vote













when you add a new custom projection to QGIS, it allocates a unique code to it and stores it in a local sqlite database (srs.db)



the first one you add is numbered 100000, the second is 100001... and numbers are allocated sequentially each time you do this. As @user30184 says, this is to prevent duplicates.



your 10027 doesn't correspond to the corresponding arcgis/spatialreference.org codes. It means that this is the 28th custom projection you've added (based on the uniqueness of the proj4 string for the projection)



The projection is shown as 'USER:10027', rather than 'ESRI:10027' or 'EPSG:10027', which suggests that it's not equivalent.






share|improve this answer























    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: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    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%2f303854%2fqgis-epsg-value-differs-from-arcgis-and-spatialreference-org%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    when you add a new custom projection to QGIS, it allocates a unique code to it and stores it in a local sqlite database (srs.db)



    the first one you add is numbered 100000, the second is 100001... and numbers are allocated sequentially each time you do this. As @user30184 says, this is to prevent duplicates.



    your 10027 doesn't correspond to the corresponding arcgis/spatialreference.org codes. It means that this is the 28th custom projection you've added (based on the uniqueness of the proj4 string for the projection)



    The projection is shown as 'USER:10027', rather than 'ESRI:10027' or 'EPSG:10027', which suggests that it's not equivalent.






    share|improve this answer



























      up vote
      2
      down vote













      when you add a new custom projection to QGIS, it allocates a unique code to it and stores it in a local sqlite database (srs.db)



      the first one you add is numbered 100000, the second is 100001... and numbers are allocated sequentially each time you do this. As @user30184 says, this is to prevent duplicates.



      your 10027 doesn't correspond to the corresponding arcgis/spatialreference.org codes. It means that this is the 28th custom projection you've added (based on the uniqueness of the proj4 string for the projection)



      The projection is shown as 'USER:10027', rather than 'ESRI:10027' or 'EPSG:10027', which suggests that it's not equivalent.






      share|improve this answer

























        up vote
        2
        down vote










        up vote
        2
        down vote









        when you add a new custom projection to QGIS, it allocates a unique code to it and stores it in a local sqlite database (srs.db)



        the first one you add is numbered 100000, the second is 100001... and numbers are allocated sequentially each time you do this. As @user30184 says, this is to prevent duplicates.



        your 10027 doesn't correspond to the corresponding arcgis/spatialreference.org codes. It means that this is the 28th custom projection you've added (based on the uniqueness of the proj4 string for the projection)



        The projection is shown as 'USER:10027', rather than 'ESRI:10027' or 'EPSG:10027', which suggests that it's not equivalent.






        share|improve this answer














        when you add a new custom projection to QGIS, it allocates a unique code to it and stores it in a local sqlite database (srs.db)



        the first one you add is numbered 100000, the second is 100001... and numbers are allocated sequentially each time you do this. As @user30184 says, this is to prevent duplicates.



        your 10027 doesn't correspond to the corresponding arcgis/spatialreference.org codes. It means that this is the 28th custom projection you've added (based on the uniqueness of the proj4 string for the projection)



        The projection is shown as 'USER:10027', rather than 'ESRI:10027' or 'EPSG:10027', which suggests that it's not equivalent.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 55 mins ago

























        answered 1 hour ago









        Steven Kay

        16.3k21553




        16.3k21553






























             

            draft saved


            draft discarded



















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgis.stackexchange.com%2fquestions%2f303854%2fqgis-epsg-value-differs-from-arcgis-and-spatialreference-org%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Trompette piccolo

            Slow SSRS Report in dynamic grouping and multiple parameters

            Simon Yates (cyclisme)