<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 102100 vs. 102113 is mixed up? in ArcGIS REST APIs and Services Questions</title>
    <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/102100-vs-102113-is-mixed-up/m-p/426381#M2051</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In 102100 and 3857, we can use an ellipsoid/spheroid-based geographic coordinate system because the map projection algorithm is handling the conversion to a sphere internally. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;102100: PROJECTION["Mercator_Auxiliary_Sphere"]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;102113: PROJECTION["Mercator"]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This parameter: PARAMETER["Auxiliary_Sphere_Type",0.0]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;determines how an ellipsoid-based GCS should be handled in a map projection that supports spheres only. The zero value means to use the semimajor axis for the sphere's radius. "1": use semiminor axis, "2": calculate authalic sphere's radius, "3": calculate authalic sphere's radius and convert geodetic latitudes to authalic latitudes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;With 102113 (3785), because the GCS was sphere-based, technically you would have to do a geographic (datum) transformation from WGS 1984 to the sphere-based GCS before the projection could occur. This is more difficult to handle because it means all data has to go through a geographic transformation. In 102100 (3857) only non-WGS84 data has to go through a geographic transformation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Both definitions give exactly the same results.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Melita&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;(edited to add sentence about results, 1:22pm PDT)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Oct 2012 19:21:51 GMT</pubDate>
    <dc:creator>MelitaKennedy</dc:creator>
    <dc:date>2012-10-03T19:21:51Z</dc:date>
    <item>
      <title>102100 vs. 102113 is mixed up?</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/102100-vs-102113-is-mixed-up/m-p/426380#M2050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I found the following in &lt;/SPAN&gt;&lt;A href="http://help.arcgis.com/en/arcgisserver/10.0/apis/rest/index.html?pcs.html"&gt;http://help.arcgis.com/en/arcgisserver/10.0/apis/rest/index.html?pcs.html&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The definition DATUM are mixed up between 102100 (3857) and 102113,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;since DATUM for 102100 should be using a sphere vs. 102113 should be using pancake.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(the same thing happens for 3857).&amp;nbsp;&amp;nbsp;&amp;nbsp; 3785 is gone from the list.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you look at the DATUM section, 102100 is using a pancake but 102113 is using sphere.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you clarify?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;102100&amp;nbsp; WGS_1984_Web_Mercator_Auxiliary_Sphere&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0]]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;102113&amp;nbsp; WGS_1984_Web_Mercator&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PROJCS["WGS_1984_Web_Mercator",GEOGCS["GCS_WGS_1984_Major_Auxiliary_Sphere",DATUM["D_WGS_1984_Major_Auxiliary_Sphere",SPHEROID["WGS_1984_Major_Auxiliary_Sphere",6378137.0,0.0]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],UNIT["Meter",1.0]]&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Oct 2012 17:59:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/102100-vs-102113-is-mixed-up/m-p/426380#M2050</guid>
      <dc:creator>YasunariTosa</dc:creator>
      <dc:date>2012-10-03T17:59:26Z</dc:date>
    </item>
    <item>
      <title>Re: 102100 vs. 102113 is mixed up?</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/102100-vs-102113-is-mixed-up/m-p/426381#M2051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;In 102100 and 3857, we can use an ellipsoid/spheroid-based geographic coordinate system because the map projection algorithm is handling the conversion to a sphere internally. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;102100: PROJECTION["Mercator_Auxiliary_Sphere"]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;102113: PROJECTION["Mercator"]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This parameter: PARAMETER["Auxiliary_Sphere_Type",0.0]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;determines how an ellipsoid-based GCS should be handled in a map projection that supports spheres only. The zero value means to use the semimajor axis for the sphere's radius. "1": use semiminor axis, "2": calculate authalic sphere's radius, "3": calculate authalic sphere's radius and convert geodetic latitudes to authalic latitudes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;With 102113 (3785), because the GCS was sphere-based, technically you would have to do a geographic (datum) transformation from WGS 1984 to the sphere-based GCS before the projection could occur. This is more difficult to handle because it means all data has to go through a geographic transformation. In 102100 (3857) only non-WGS84 data has to go through a geographic transformation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Both definitions give exactly the same results.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Melita&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;(edited to add sentence about results, 1:22pm PDT)&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Oct 2012 19:21:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/102100-vs-102113-is-mixed-up/m-p/426381#M2051</guid>
      <dc:creator>MelitaKennedy</dc:creator>
      <dc:date>2012-10-03T19:21:51Z</dc:date>
    </item>
  </channel>
</rss>

