Select to view content in your preferred language

FeatureLayer Default Symbology/Renderer

2006
3
04-29-2011 12:34 PM
TonyThatcher
Deactivated User
Hopefully somebody can shed some light on this issue.

We have a map service that has a bit of custom defined symbology (e.g. Roads of different classes get displayed or labeled in certain ways).  When I add this service to my Silverlight Map as an ArcGISDynamicMapServiceLayer, the symbology comes through perfectly.  From other posts it appears that this is the default renderer for the layer (I can override it if I want by defining my on renderer in the XAML).  But for certain maps it makes sense to only show a subset of the layers, so I am loading these individual layers as Feature Layers.  When I do this, the default symbology disappears.  I really do not want to define my symbology/renderers in XAML when it is already defined in the map service.

Am I missing something?  Is this behavior by design.  I can't find any discussion of it directly in the documentation, but an ESRI staffer seemed to indicate on another post that the only way to override the default renderer from the Map Service was to define my own.  So this seems to indicate that the default renderer from the Map Service should be the same no matter if it is loaded along with all the other layers as a ArcGISDynamicMapServiceLayer or as a single layer using a FeatureLayer.

Ideas?

-Tony
0 Kudos
3 Replies
DominiqueBroux
Esri Frequent Contributor

I am loading these individual layers as Feature Layers. When I do this, the default symbology disappears.

Which ArcGIS server version are you using? 
The default feature layer symbology is a new functionality of ArcGIS server 10.0.
So if you are using a prior version this explains your issue.
0 Kudos
TonyThatcher
Deactivated User
Server 9.3, currently.  So is there any way to use the Server-defined symbology using DataLayers?  Or do I have to set the renderer for each data layer?

-Tony
0 Kudos
DominiqueBroux
Esri Frequent Contributor
In 9.3 the server-defined symbology is not exposed by the REST API, so unfortunately you have to define it by yourself at the client side (or migrate to 10...)
0 Kudos