<?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 Planning ArcServer Services - Bare Feature Class or Customized MXD? in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/planning-arcserver-services-bare-feature-class-or/m-p/595998#M23010</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am in the process of overhauling a directory of REST services and was interested to know if there are any best practices based on intended use.&amp;nbsp; Nearly all of the services are designed to be consumed through AGOL web maps\apps or Business Analyst Online.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The question???&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Is it better to create "standard" services based on the feature class and allow the user to further customize within each map/app or to create the service based on an MXD with predefined symbology, number of layers, and filtering?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If the first methodology is taken, then multiple copies of the same service are often needed to create the intended information package within the map/app.&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;If the second methodology is taken, then customization is limited, but much less setup is required to reach the intended result within the map/app.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to avoid creating a number of variations of the same service while also trying to standardize the output of the information.&amp;nbsp; While the answer will be somewhat opinion, any guidance or suggestion(s) would be greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 May 2016 14:41:54 GMT</pubDate>
    <dc:creator>BryanChandler1</dc:creator>
    <dc:date>2016-05-25T14:41:54Z</dc:date>
    <item>
      <title>Planning ArcServer Services - Bare Feature Class or Customized MXD?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/planning-arcserver-services-bare-feature-class-or/m-p/595998#M23010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am in the process of overhauling a directory of REST services and was interested to know if there are any best practices based on intended use.&amp;nbsp; Nearly all of the services are designed to be consumed through AGOL web maps\apps or Business Analyst Online.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The question???&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Is it better to create "standard" services based on the feature class and allow the user to further customize within each map/app or to create the service based on an MXD with predefined symbology, number of layers, and filtering?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If the first methodology is taken, then multiple copies of the same service are often needed to create the intended information package within the map/app.&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;If the second methodology is taken, then customization is limited, but much less setup is required to reach the intended result within the map/app.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to avoid creating a number of variations of the same service while also trying to standardize the output of the information.&amp;nbsp; While the answer will be somewhat opinion, any guidance or suggestion(s) would be greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 May 2016 14:41:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/planning-arcserver-services-bare-feature-class-or/m-p/595998#M23010</guid>
      <dc:creator>BryanChandler1</dc:creator>
      <dc:date>2016-05-25T14:41:54Z</dc:date>
    </item>
  </channel>
</rss>

