<?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: Converting Features to Graphics for services. in Developers Questions</title>
    <link>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477224#M3197</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If all you need is to have these (building footprints, parcels, roads) as basemap/reference layers, then probably the best performance you'd get is to create a tiled map service for these.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Jan 2016 01:14:58 GMT</pubDate>
    <dc:creator>EricBader</dc:creator>
    <dc:date>2016-01-06T01:14:58Z</dc:date>
    <item>
      <title>Converting Features to Graphics for services.</title>
      <link>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477222#M3195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if there is any reasons to convert Features to Graphics in order to improve performance for published services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My situation is I have building footprints, which is of course a polygon feature class, but if I convert them to graphics does this make the performance better in mobile apps?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If performance would be improved, I would probably do this for the footprints, parcels and roads all as my basemap?&amp;nbsp; Just checking to see if anyone has ever looked into this?&amp;nbsp; I couldn't find anything online about the performance aspect.&amp;nbsp; Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Jan 2016 21:58:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477222#M3195</guid>
      <dc:creator>JASONREMILLARD</dc:creator>
      <dc:date>2016-01-05T21:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: Converting Features to Graphics for services.</title>
      <link>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477223#M3196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can find no reason or suggestion posted to think that graphics would improve performance.&amp;nbsp; Reducing redundant geometries and attributes I can see as a possibility.&amp;nbsp; I suspect you will have to experiment yourself using either choice to see if there is any improvement, since your data cannot be replicated by others&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Jan 2016 22:24:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477223#M3196</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2016-01-05T22:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Converting Features to Graphics for services.</title>
      <link>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477224#M3197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If all you need is to have these (building footprints, parcels, roads) as basemap/reference layers, then probably the best performance you'd get is to create a tiled map service for these.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2016 01:14:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-questions/converting-features-to-graphics-for-services/m-p/477224#M3197</guid>
      <dc:creator>EricBader</dc:creator>
      <dc:date>2016-01-06T01:14:58Z</dc:date>
    </item>
  </channel>
</rss>

