Select to view content in your preferred language

FeatureService symbology for SimpleLineSymbols

1022
3
12-14-2010 10:47 AM
AndrewMalander
Emerging Contributor
I have noticed when creating SimpleLineSymbol symbology for polylines to use in the Editor in API 2.1 (and previously) that all the line styles work except DOT.  It appears the enum conversion from desktop to server for line styles flips NULL and DOT.

Also, although there is a CartographicLineSymbol in the ESRI Silverlight API, the editor/template picker seems to ignore the use of those types as regards their pattern and render plain lines.

Is this a known issue? Am i doing something wrong?
0 Kudos
3 Replies
JenniferNery
Esri Regular Contributor
Can you share us your FeatureService DrawingInfo?

If you append "?f=pjson" to your FeatureService URL in your web browser, kindly copy and paste the section for "drawingInfo" when you reply to this thread.

"esriSLSDot" as LineStyle should be respected.

Also if you can, can you give us a snapshot of this symbol? Does it show different when viewed in ArcGIS.com?
0 Kudos
AndrewMalander
Emerging Contributor
Thanks for the response.  Here is the drawingInfo:

"drawingInfo" : {"renderer" :
    {
      "type" : "uniqueValue",
      "field1" : "SUBTYPE",
      "field2" : null,
      "field3" : null,
      "fieldDelimiter" : ", ",
      "defaultSymbol" :
      {
        "type" : "esriSLS",
        "style" : "esriSLSSolid",
       
        "color" : [
          82,
          0,
          158,
          255
        ],
        "width" : 1
      },
      "defaultLabel" : "\u003call other values\u003e",
      "uniqueValueInfos" : [
        {
          "value" : "0",
          "label" : "Black",
          "description" : "",
          "symbol" :
          {
            "type" : "esriSLS",
            "style" : "esriSLSSolid",
           
            "color" : [
              0,
              0,
              0,
              255
            ],
            "width" : 1
          }
        },
        {
          "value" : "2",
          "label" : "Blue",
          "description" : "",
          "symbol" :
          {
            "type" : "esriSLS",
            "style" : "esriSLSDash",
           
            "color" : [
              0,
              92,
              230,
              255
            ],
            "width" : 1
          }
        },
        {
          "value" : "3",
          "label" : "Green",
          "description" : "",
          "symbol" :
          {
            "type" : "esriSLS",
            "style" : "esriSLSDot",
           
            "color" : [
              76,
              230,
              0,
              255
            ],
            "width" : 1
          }
        },
        {
          "value" : "4",
          "label" : "Orange",
          "description" : "",
          "symbol" :
          {
            "type" : "esriSLS",
            "style" : "esriSLSDashDot",
           
            "color" : [
              230,
              76,
              0,
              255
            ],
            "width" : 1
          }
        },
        {
          "value" : "1",
          "label" : "Red",
          "description" : "",
          "symbol" :
          {
            "type" : "esriSLS",
            "style" : "esriSLSDashDotDot",
           
            "color" : [
              230,
              0,
              0,
              255
            ],
            "width" : 1
          }
        }
      ]
    },
    "transparency" : 0,
    "labelingInfo" : null},
  "hasAttachments" : false,
  "htmlPopupType" : "esriServerHTMLPopupTypeAsHTMLText",
  "objectIdField" : "OBJECTID",
  "globalIdField" : "",
  "typeIdField" : "SUBTYPE",



Here is the Editor when it is displayed:
0 Kudos
JenniferNery
Esri Regular Contributor
Thank you for reporting this. I was able to replicate the issue. We missed to support "esriSLSDot" in v2.1. We will try to get this fixed in future releases.
0 Kudos