CIMSymbol not tiling correctly

1642
5
Jump to solution
03-27-2023 12:12 PM
JamesIng
New Contributor III

Hi there, we've been playing with the CIMSymbol and have created a simple symbol comprised of a base color and three hatch fills ontop. The hatch fills are rotated 45, 90, and 135.

But we're noticed on more than one occasion the symbol doesn't tile correctly and the hatch fills 'break' along the tile.

In this image you can see the CIMSymbol - as well as a enlarged close up to show the mis-alignment.

JamesI_0-1679943957106.png


The symbol itself doesn't have anything fancy like primitive overrides or anything.

Has anyone encountered this tiling issue?

Symbol for reference

 

{
  "type": "CIMPolygonSymbol",
  "symbolLayers": [
    {
      "type": "CIMSolidStroke",
      "enable": true,
      "capStyle": "Round",
      "joinStyle": "Round",
      "lineStyle3D": "Strip",
      "miterLimit": 10,
      "width": 0.4,
      "color": [0, 0, 0, 255]
    },
    {
      "type": "CIMHatchFill",
      "enable": true,
      "lineSymbol": {
        "type": "CIMLineSymbol",
        "symbolLayers": [
          {
            "type": "CIMSolidStroke",
            "enable": true,
            "capStyle": "Butt",
            "joinStyle": "Miter",
            "lineStyle3D": "Strip",
            "miterLimit": 10,
            "width": 0.5,
            "color": [255, 255, 255, 255]
          }
        ]
      },
      "rotation": 90,
      "separation": 10
    },
    {
      "type": "CIMHatchFill",
      "enable": true,
      "lineSymbol": {
        "type": "CIMLineSymbol",
        "symbolLayers": [
          {
            "type": "CIMSolidStroke",
            "enable": true,
            "capStyle": "Butt",
            "joinStyle": "Miter",
            "lineStyle3D": "Strip",
            "miterLimit": 10,
            "width": 0.5,
            "color": [255, 255, 255, 255]
          }
        ]
      },
      "rotation": 135,
      "separation": 10
    },
    {
      "type": "CIMHatchFill",
      "enable": true,
      "lineSymbol": {
        "type": "CIMLineSymbol",
        "symbolLayers": [
          {
            "type": "CIMSolidStroke",
            "enable": true,
            "capStyle": "Butt",
            "joinStyle": "Miter",
            "lineStyle3D": "Strip",
            "miterLimit": 10,
            "width": 0.5,
            "color": [255, 255, 255, 255]
          }
        ]
      },
      "rotation": 45,
      "separation": 10
    },
    {
      "type": "CIMSolidFill",
      "enable": true,
      "color": [39, 129, 153, 255]
    }
  ]
}

 

 

James from www.landkind.com
Tags (2)
0 Kudos
2 Solutions

Accepted Solutions
AnneFitz
Esri Regular Contributor

Thanks! I'm able to reproduce, but only at large scales. Do you still see the tiling issue if you zoom out a bit? 

Anyways, we'll look into this! Thanks for reporting.

View solution in original post

AnneFitz
Esri Regular Contributor

Hi @JamesIng , we've installed a fix for this for the June (4.27) release. It is available for testing now on the development version of the API, https://js.arcgis.com/next. Let us know if you are still running into any issues, and you can expect this fix in the upcoming release of the API in June! 

View solution in original post

5 Replies
AnneFitz
Esri Regular Contributor

Hi @JamesIng - what version of the API are you using?

0 Kudos
JamesIng
New Contributor III

Hi Anne,

We're using 4.25.5 via arcGIS/core

James from www.landkind.com
0 Kudos
AnneFitz
Esri Regular Contributor

Thanks! I'm able to reproduce, but only at large scales. Do you still see the tiling issue if you zoom out a bit? 

Anyways, we'll look into this! Thanks for reporting.

JamesIng
New Contributor III

Doesnt appear to happen when zoomed out.- but that's potentially due to our geometry not being large enough for it tile at that scale.


James from www.landkind.com
0 Kudos
AnneFitz
Esri Regular Contributor

Hi @JamesIng , we've installed a fix for this for the June (4.27) release. It is available for testing now on the development version of the API, https://js.arcgis.com/next. Let us know if you are still running into any issues, and you can expect this fix in the upcoming release of the API in June!