You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking with @donflopez and understanding the constraints of all default properties for polygon features blocking vector rendering, we decided, let's go ahead and remove them.
These properties are specifically for smoother rendering between polygons and lines and are more important for things like choropleth maps.
But with vector rendering, we are noticing better lines on the published map than with raster:
In addition, anytime you change styling in the forms the polygon-gamma and line-comp-op properties are reset and no longer persist through to the users styling.
We can go ahead and remove the properties that are blocking and default to the CartoCSS below for polygon fills:
rochoa
changed the title
Remove default styling properties for polygons that aren't supported for vector
[Vector] Remove default styling properties for polygons that aren't supported for vector
Jun 21, 2017
After talking with @donflopez and understanding the constraints of all default properties for polygon features blocking vector rendering, we decided, let's go ahead and remove them.
These properties are specifically for smoother rendering between polygons and lines and are more important for things like choropleth maps.
But with vector rendering, we are noticing better lines on the published map than with raster:
In addition, anytime you change styling in the forms the
polygon-gamma
andline-comp-op
properties are reset and no longer persist through to the users styling.We can go ahead and remove the properties that are blocking and default to the CartoCSS below for polygon fills:
Which with vector will look like this:

cc @saleiva
The text was updated successfully, but these errors were encountered: