<?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: Export Web Map and legend color oddness - ArcGIS for Server 10.1 in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/export-web-map-and-legend-color-oddness-arcgis-for/m-p/106549#M4137</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'll provide my own 'solution' here. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; We're talking ArcGIS 10.1, no service pack, if it makes a difference.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem is that publishing only takes 'half' of the symbology for a more complex case.&amp;nbsp; Example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have two GP output feature sets.&amp;nbsp; One simply symbolizes all shapes with a border color, irrespective of feature contents.&amp;nbsp; The other symbolizes based on a type field within each feature.&amp;nbsp; Both symbologies are set directly on the ModelBuilder output parameters.&amp;nbsp; When the model is run in ArcMap, the results are correctly symbolized on screen for both feature sets.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's publishing the result that is the problem.&amp;nbsp; If I publish the result without changes, the first, simple map service symbolizes correctly.&amp;nbsp; The second, complex case, however, takes only 'half' of the symbology.&amp;nbsp; The features are correctly discriminated in terms of the type field, so the break is correct and the features are identifiable by type, but the colors are not carried over.&amp;nbsp; Rather, a default set of colors seems to be applied.&amp;nbsp; Meaning that I can see something is a 'plant', but it's bright red, instead of green.&amp;nbsp; This is particularly problematic if the original layer that was subset to produce the output already uses bright red for another type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The solution is to re-apply the layer files to the outputs on the map before publishing the result.&amp;nbsp; I know this is what the docs say to do, but I don't understand why the 'half-cooked' situation is happening.&amp;nbsp; Well, I suspect a bug, but there you go.&amp;nbsp; It would be wonderful if a model could fully encapsulate the treatment of its outputs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Frank&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Feb 2013 14:00:37 GMT</pubDate>
    <dc:creator>FrankMcLean</dc:creator>
    <dc:date>2013-02-26T14:00:37Z</dc:date>
    <item>
      <title>Export Web Map and legend color oddness - ArcGIS for Server 10.1</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/export-web-map-and-legend-color-oddness-arcgis-for/m-p/106548#M4136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a geoprocessing service which exports its results as a map service.&amp;nbsp; I use this to produce a printable map via the Export Web Map utility.&amp;nbsp; The issue I'm having is the seemingly odd designation of colors for the output layer.&amp;nbsp; I've symbolized the output with the exact same layer file I use for the input (output is basically a subset of input) and the colors are completely different, though consistently (as far as I can tell) completely different, i.e. the same odd palate is used each time.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone have any clues?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Frank&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 18:18:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/export-web-map-and-legend-color-oddness-arcgis-for/m-p/106548#M4136</guid>
      <dc:creator>FrankMcLean</dc:creator>
      <dc:date>2013-02-19T18:18:03Z</dc:date>
    </item>
    <item>
      <title>Re: Export Web Map and legend color oddness - ArcGIS for Server 10.1</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/export-web-map-and-legend-color-oddness-arcgis-for/m-p/106549#M4137</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'll provide my own 'solution' here. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; We're talking ArcGIS 10.1, no service pack, if it makes a difference.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem is that publishing only takes 'half' of the symbology for a more complex case.&amp;nbsp; Example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have two GP output feature sets.&amp;nbsp; One simply symbolizes all shapes with a border color, irrespective of feature contents.&amp;nbsp; The other symbolizes based on a type field within each feature.&amp;nbsp; Both symbologies are set directly on the ModelBuilder output parameters.&amp;nbsp; When the model is run in ArcMap, the results are correctly symbolized on screen for both feature sets.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's publishing the result that is the problem.&amp;nbsp; If I publish the result without changes, the first, simple map service symbolizes correctly.&amp;nbsp; The second, complex case, however, takes only 'half' of the symbology.&amp;nbsp; The features are correctly discriminated in terms of the type field, so the break is correct and the features are identifiable by type, but the colors are not carried over.&amp;nbsp; Rather, a default set of colors seems to be applied.&amp;nbsp; Meaning that I can see something is a 'plant', but it's bright red, instead of green.&amp;nbsp; This is particularly problematic if the original layer that was subset to produce the output already uses bright red for another type.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The solution is to re-apply the layer files to the outputs on the map before publishing the result.&amp;nbsp; I know this is what the docs say to do, but I don't understand why the 'half-cooked' situation is happening.&amp;nbsp; Well, I suspect a bug, but there you go.&amp;nbsp; It would be wonderful if a model could fully encapsulate the treatment of its outputs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Frank&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 14:00:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/export-web-map-and-legend-color-oddness-arcgis-for/m-p/106549#M4137</guid>
      <dc:creator>FrankMcLean</dc:creator>
      <dc:date>2013-02-26T14:00:37Z</dc:date>
    </item>
  </channel>
</rss>

