nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Thousands Separator for Label Expression using Python

ChrisDonohue__GISP

How does one use Python to format a number label so it shows the thousands separator? For example, I have a value of 12345 that I want to display (from the Shape.Area field of a File Geodatabase feature class) on the map as a label as 12,345.

I looked at these discussions, but can't seem to get it to work.

What is label expression for formatting a number to have thousands separator and decimals?

python - Add 'decimal-mark' thousands separators to a number - Stack Overflow

I guess I could slice the value and insert commas, but I was hoping to use something easier.

I'm using ArcGIS 10.2.1 (so Python 2.7.5). I'm a beginner in Python, so there is a good chance I am just missing something basic in trying to do this.

Chris Donohue, GISP

Find more posts tagged with

Accepted answers

DarrenWiens2

Hmmm... this works for me (field type is Long):

<SPAN class="keyword token">def</SPAN> FindLabel <SPAN class="punctuation token">(</SPAN> <SPAN class="punctuation token">[</SPAN>CLIENTNUM<SPAN class="punctuation token">]</SPAN> <SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp; <SPAN class="keyword token">return</SPAN> <SPAN class="string token">"{:,}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>float<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN>CLIENTNUM<SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

All comments

ClintonDow1

Hi Dan, I agree. I had to do a bit of digging to figure that out so I don't think its common knowledge but I'll definitely recommend that we mention it in the docs.

DanPatterson_Retired

Clinton, this would be a nice inclusion in the help topics. It may not matter for most, but if casting is needed because a python object is used, then this means something to some of us.

This is going to be an issue when people start migrating to Pro and start using Pandas which makes judicious use of python's object... most people will think

... if it looks like a number, it should act like a number...

Indicating in the help that casting to float or string (I wont get into python 2 vs 3 'strings') should be used explicitly would at least warn people. A few simple examples would also help. I know that you aren't the person to implement this in the help, but I have a strong suspicion that the doc's people aren't big on object casting and representation.

Thanks

ClintonDow1

Hi Chris,

The cast is necessary because the field's value is returned as an object (that is, the Python base class), since arbitrary data types are supported by the expression dialog. String.format() does not work with uncast objects because an object.__repr__ method returns a 'method-wrapper' class and not a datatype that string.format knows how to work with. Once you've cast the object, in this case invoking its __float__ method, it returns its value as a float data type which plays nice with string formatting.

ChrisDonohue__GISP

That worked! Thanks Darren.

Chris Donohue, GISP

DarrenWiens2

Python parser, and I don't recall if I selected from the list or not, but it's correct. The label expression box doesn't use the normal !Field! notation, just to keep you on your toes.

DanPatterson_Retired

was that with the python parser and selecting the fields from the list? or by keying everything in? That is one of the things Chris needs to figure out ... is it the process that is causing the error or the parser?

DarrenWiens2

Hmmm... this works for me (field type is Long):

<SPAN class="keyword token">def</SPAN> FindLabel <SPAN class="punctuation token">(</SPAN> <SPAN class="punctuation token">[</SPAN>CLIENTNUM<SPAN class="punctuation token">]</SPAN> <SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp; <SPAN class="keyword token">return</SPAN> <SPAN class="string token">"{:,}"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>float<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN>CLIENTNUM<SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

DanPatterson_Retired

so even str(!SHAPE_area!) errors out? I am just wondering if the output is supposed to be string.

In any event, I don't do labelling, but I would be a tad peeved if Verify says nothing about what was wrong and more importantly, if the python parser is defective. Good luck

ChrisDonohue__GISP

I was noticing that too. It doesn't matter if the Parser in the Label Expression is changed to Python first or not, the field names come across with brackets when one double-clicks on the field you want to select it. On top of that, if one changes the field name to be surrounded by exclamation marks instead of brackets(with Python still selected as the Parser) it errors out:

As for the one-space indentation, it is actually two spaces and that seems to be what ArcGIS defaults to.

Chris Donohue, GISP

DanPatterson_Retired

python parser.... then why are the fieldnames enclosed in square brackets instead of ! ! ?? Is this unique to labelling? Chris, I don't do much labelling, but did you pick the parser before building the expression or after? and what's up with the one space indentation? does Arc* put that indentation in or is that you?

ChrisDonohue__GISP

If I purely use a number in the format, it works correctly. But now the catch, how do I substitute in SHAPE_Area so it labels based on that field that with comma separators instead of a hard-coded number?

Chris Donohue, GISP

Brittney White

From Building label expressions: "Field values are automatically cast to text strings. Therefore, if you wish to use a numeric value in an arithmetic operation, or when making a comparison, you will need to cast it back to a numeric data type."

This could look something like:

"{:,}".format(float([Field_Name]) )

DanPatterson_Retired

>>> "{:,}".format(1000000)
'1,000,000'

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.