Character marker symbols much larger than in previous ArcMap versions

1090
4
11-20-2016 04:15 AM
MihkelMänna
Occasional Contributor

I've created a number of Character Marker Symbols in ArcMap 10.2.x. When trying to edit these symbols in ArcMap 10.4.1, the symbols get much (10-20 times) larger than expected, thus making them unusable for my map designs. This is true for all fonts, plus I have experienced this on two different machines.

Has could I possibly solve this problem? Any help would be appreciated!

0 Kudos
4 Replies
DanPatterson_Retired
MVP Emeritus

since you are using glyphs etc from text fonts, then the only possibilities in a difference in how text is being interpreted between your previous installation of arcmap and the current.

Understanding text font size—Help | ArcGIS for Desktop 

What were they previously defined in or was there a switch in units somewhere

0 Kudos
MihkelMänna
Occasional Contributor

Thanks for the response, Dan!

I tested the symbols in ArcMap 10.2.1 and I'll illustrate my problem a little more. There the units are in millimeters (see fig 1) and when changing the size, everything works as expected. One can change the units and the size value changes accordingly, not affecting the symbol's appearance.

Fig 1

Now in ArcMap 10.4.1., at first the symbols are also in millimeters or points (no idea, what it depends on) and the symbol looks as expected (same as in fig 1). But when changing the symbol's size value, the symbol's size becomes much larger than expected (even if decreasing the size - see fig 2).

Fig 2

When changing the initial symbol's size units, the symbol disappears (fig 3) and a number of error messages with the same (or similar) text appear on screen one after another (fig 4).

Fig 3

Fig 4

I can't get my head around it, but unfortunately it does not seem to be a simple units issue. Any more ideas?

0 Kudos
MihkelMänna
Occasional Contributor

One more thing: this behavior also affects newly created symbols, which means that I cannot create as small symbols I'd need.

0 Kudos
MihkelMänna
Occasional Contributor

Well, it seems now that it was an OS decimal separator issue. The machine that created those symbols used comma as a separator, and the other machines used periods. Although my sizes didn't have decimals, the program went completely berserk trying to parse the size value. Lesson learned.