<?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: Anti-aliasing with Services in Shared Pooling in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180060#M7149</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm also experiencing this.&amp;nbsp; The shared instances are otherwise a wonderful thing to have, but I was heartbroken when I discovered all the jagged lines in my web map; switching the service to use a dedicated instance made everything pretty again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Nov 2019 22:24:41 GMT</pubDate>
    <dc:creator>MichaelMorisette</dc:creator>
    <dc:date>2019-11-22T22:24:41Z</dc:date>
    <item>
      <title>Anti-aliasing with Services in Shared Pooling</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180059#M7148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I really like the idea of shared pooling instances with the latest releases of ArcGIS Server.&amp;nbsp; Rather than having dedicated SOC instances running, we can dedicate certain services to participate in the shared pool to save server resources.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing I have noticed with services participating in the shared pool is that anti-aliasing is not honored for these services.&amp;nbsp; Once I remove a service from the shared pool, I notice anti-aliasing is honored.&amp;nbsp; I'm just curious why this is?...and if this is something that can be changed / implemented in future releases?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know this may be a small issue for some, but as someone who enjoys good looking maps, it's one thing I notice right away with services.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Sep 2019 19:26:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180059#M7148</guid>
      <dc:creator>mpboyle</dc:creator>
      <dc:date>2019-09-17T19:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: Anti-aliasing with Services in Shared Pooling</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180060#M7149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm also experiencing this.&amp;nbsp; The shared instances are otherwise a wonderful thing to have, but I was heartbroken when I discovered all the jagged lines in my web map; switching the service to use a dedicated instance made everything pretty again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Nov 2019 22:24:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180060#M7149</guid>
      <dc:creator>MichaelMorisette</dc:creator>
      <dc:date>2019-11-22T22:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: Anti-aliasing with Services in Shared Pooling</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180061#M7150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI, there is a bug logged with Tech Support for this issue: BUG-000125833&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Nov 2019 22:29:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/anti-aliasing-with-services-in-shared-pooling/m-p/180061#M7150</guid>
      <dc:creator>AbraamPankhurst</dc:creator>
      <dc:date>2019-11-22T22:29:54Z</dc:date>
    </item>
  </channel>
</rss>

