<?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 Why is a TPK I exported from a map service a different size when using ArcMap vs Arcpy? Both missing tiles when published on AGOL in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/why-is-a-tpk-i-exported-from-a-map-service-a/m-p/200912#M7862</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Exporting a tpk from a Map Service tile cache.&lt;/P&gt;&lt;P&gt;When exporting from ArcMap(10.4; ArcGIS Server 10.5) I get a smaller sized TPK then when I use the arcpy tool; both are using the same exact parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Export to Tile Package&lt;/P&gt;&lt;P&gt;- Compact&lt;/P&gt;&lt;P&gt;- Area of Interest set with a Feature Layer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I exported the feature layer I was using in arcpy to a feature class and checked the extent in ArcMap, it is slightly larger than the one produced in ArcMap with no code; however, when I check the inputs to the tool in geoprocessing results they both are exporting at the same extents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then I am noticing more issues once I bring either of these to AGOL...they're missing tiles (less tiles than the expected amount) but weirdly they both seem to cover the AOI at all the intended scales.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This later part is making me start to think, is the problem stemming from the map server cache itself? I am going to delete it and make a new one, though it so large this will take hours. Hoping in the meantime someone could offer me some insight on what is going on, thanks!&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Apr 2020 20:22:32 GMT</pubDate>
    <dc:creator>CarlVricella</dc:creator>
    <dc:date>2020-04-14T20:22:32Z</dc:date>
    <item>
      <title>Why is a TPK I exported from a map service a different size when using ArcMap vs Arcpy? Both missing tiles when published on AGOL</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/why-is-a-tpk-i-exported-from-a-map-service-a/m-p/200912#M7862</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Exporting a tpk from a Map Service tile cache.&lt;/P&gt;&lt;P&gt;When exporting from ArcMap(10.4; ArcGIS Server 10.5) I get a smaller sized TPK then when I use the arcpy tool; both are using the same exact parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Export to Tile Package&lt;/P&gt;&lt;P&gt;- Compact&lt;/P&gt;&lt;P&gt;- Area of Interest set with a Feature Layer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I exported the feature layer I was using in arcpy to a feature class and checked the extent in ArcMap, it is slightly larger than the one produced in ArcMap with no code; however, when I check the inputs to the tool in geoprocessing results they both are exporting at the same extents.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then I am noticing more issues once I bring either of these to AGOL...they're missing tiles (less tiles than the expected amount) but weirdly they both seem to cover the AOI at all the intended scales.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This later part is making me start to think, is the problem stemming from the map server cache itself? I am going to delete it and make a new one, though it so large this will take hours. Hoping in the meantime someone could offer me some insight on what is going on, thanks!&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Apr 2020 20:22:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/why-is-a-tpk-i-exported-from-a-map-service-a/m-p/200912#M7862</guid>
      <dc:creator>CarlVricella</dc:creator>
      <dc:date>2020-04-14T20:22:32Z</dc:date>
    </item>
  </channel>
</rss>

