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
I've been doing some testing, and it looks like until point sizes are set to 7 that the rendering of them in the point legends is either unreadable (too small) or not circular. I'm wondering if there is a way for us to set a default minimum point size for legends to avoid this issue... when there is a lot of data on the map, naturally, users will symbolize with smaller point sizes so I think adding in some defaults around this would prove extremely useful for them.
Here is an example of point legends from size=2 to size=7 so you can visually see what I am referring to:
Size 2:
Size 3:
Size 4:
Size 5:
Size 6:
Size 7:
While I didn't go through the same exercise for lines, you can see that the lowest (top) category line is offset and not centered with the rest.. and through previous use know that there are similar issues with line widths:
The text was updated successfully, but these errors were encountered:
@elenatorro @Jesus89 for discussion.
I've been doing some testing, and it looks like until point sizes are set to
7
that the rendering of them in the point legends is either unreadable (too small) or not circular. I'm wondering if there is a way for us to set a default minimum point size for legends to avoid this issue... when there is a lot of data on the map, naturally, users will symbolize with smaller point sizes so I think adding in some defaults around this would prove extremely useful for them.Here is an example of point legends from
size=2
tosize=7
so you can visually see what I am referring to:Size 2:
Size 3:
Size 4:
Size 5:
Size 6:
Size 7:
While I didn't go through the same exercise for lines, you can see that the lowest (top) category line is offset and not centered with the rest.. and through previous use know that there are similar issues with line widths:
The text was updated successfully, but these errors were encountered: