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; } } }

Rounding issues using Python in ArcGIS Pro

AdrianWelsh

It seems to me that ArcGIS Pro is not rounding my numbers correctly when I use Python in Calculate Field. Or my expression is incorrect.

Here is my example:

The Shape_Area of a feature is 7464.72748

My Calculate Field expression is

str(int(round(round(!Shape_Area!), -1)))<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

I would think this should result in a string value of 7470, but it gave me 7460.

Where am I going wrong? Shouldn't round(7464.72748) give me 7465 more or less?

And then round(7465, -1) give me 7470?

Find more posts tagged with

Accepted answers

DanPatterson_Retired

dozens of ways.... time to explore, this will get you going.

<SPAN class="keyword token">import</SPAN> math&nbsp; <SPAN class="comment token"># which is available in arcmap and the field calculator</SPAN>
math<SPAN class="punctuation token">.</SPAN>ceil<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">2726</SPAN>

int<SPAN class="punctuation token">(</SPAN>math<SPAN class="punctuation token">.</SPAN>ceil<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN> <SPAN class="operator token">/</SPAN> <SPAN class="number token">10.0</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">*</SPAN> <SPAN class="number token">10</SPAN>
<SPAN class="number token">2730</SPAN>

<SPAN class="comment token"># or if you understand base 9 and base 10 differences</SPAN>

<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN><SPAN class="operator token">+</SPAN><SPAN class="number token">9</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="operator token">//</SPAN><SPAN class="number token">10</SPAN> <SPAN class="operator token">*</SPAN><SPAN class="number token">10</SPAN>
<SPAN class="number token">2730.0</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

plus some numpy stuff.... the rest are tricks etc

Excel makes people dependent on masking the tricks that us old timers relied upon for years.

All comments

DanPatterson_Retired

You are now in python 3... did you see the docs first? It works as expected

https://docs.python.org/3/library/functions.html#round

a <SPAN class="operator token">=</SPAN> <SPAN class="number token">7464.72748</SPAN>

round<SPAN class="punctuation token">(</SPAN>a<SPAN class="punctuation token">,</SPAN> <SPAN class="number token">1</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">7464.7</SPAN>

round<SPAN class="punctuation token">(</SPAN>a<SPAN class="punctuation token">,</SPAN> <SPAN class="number token">0</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">7465.0</SPAN>

round<SPAN class="punctuation token">(</SPAN>a<SPAN class="punctuation token">,</SPAN> <SPAN class="operator token">-</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">7460.0</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

skip the round round round thing, that will get confusing

AdrianWelsh

I was wondering if Python 3 had anything to do with it since when I carried out the expression in Python 2, it worked as expected.

So, to get this straight, Python no longer rounds like normal arithmetic (like Excel would do). It rounds to the nearest even number first, unless it's far down the decimal chain, then it's "surprising" as the text puts it.

The round round was due to having to join up a table in Excel that had already rounded once - it's complicated but worked better than just one round.

So, is there way to round like Excel rounds?

For another example, when Shape_Area is 2725.059761, how do I make it round to 2730 versus 2720 (like I would in Excel and normal arithmetic)?

DanPatterson_Retired

dozens of ways.... time to explore, this will get you going.

<SPAN class="keyword token">import</SPAN> math&nbsp; <SPAN class="comment token"># which is available in arcmap and the field calculator</SPAN>
math<SPAN class="punctuation token">.</SPAN>ceil<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="number token">2726</SPAN>

int<SPAN class="punctuation token">(</SPAN>math<SPAN class="punctuation token">.</SPAN>ceil<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN> <SPAN class="operator token">/</SPAN> <SPAN class="number token">10.0</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">*</SPAN> <SPAN class="number token">10</SPAN>
<SPAN class="number token">2730</SPAN>

<SPAN class="comment token"># or if you understand base 9 and base 10 differences</SPAN>

<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2725.059761</SPAN><SPAN class="operator token">+</SPAN><SPAN class="number token">9</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="operator token">//</SPAN><SPAN class="number token">10</SPAN> <SPAN class="operator token">*</SPAN><SPAN class="number token">10</SPAN>
<SPAN class="number token">2730.0</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

plus some numpy stuff.... the rest are tricks etc

Excel makes people dependent on masking the tricks that us old timers relied upon for years.

AdrianWelsh

Wow, this is good stuff to explore. I'm not sure I want to use the ceiling function since I don't always want it to round up.

But, since this is really only for joining tables together to make a simple match, I can force excel to do the same. It looks like the function is this:

=CEILING.MATH(2725.059761,10) results in 2730

Base 9 and 10?!? That's a thinker. I'll play around with that some... until my head hurts!

JoshuaBixby

What’s New In Python 3.0 — Python 3.6.4 documentation :

The round() function rounding strategy and return type have changed. Exact halfway cases are now rounded to the nearest even result instead of away from zero. (For example, round(2.5) now returns 2 rather than 3.) round(x[, n]) now delegates to x.__round__(<N>)</N> instead of always returning a float. It generally returns an integer when called with a single argument and a value of the same type as x when called with two arguments.

DanPatterson_Retired

we are using 3.6 in PRO, my test environment

MarcoBoeringa

Please also have a look at the "decimal" module of Python:

https://docs.python.org/3.6/library/decimal.html

It may offer functions you need as well. You can import the module in e.g. the Calculate Field tool.

AdrianWelsh

Rounding is ridiculous.

Joining up an "engineer's" spreadsheet with sorta-rounded-area numbers (integers) with a converted CAD drawing takes more effort than it should. This is what my code block Calculate Field expression had to look like to get as close as I could (though, I likely could have gotten closer with more ceilinging and flooring, but I got lazy):

import math
def ceiling(parcel, area):
&nbsp;&nbsp;&nbsp; return str(parcel) + " - " + str(int(math.ceil(math.floor(area) / 10)) * 10)

__esri_field_calculator_splitter__

ceiling(!Parcel!, !Shape_Area!)<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

thanks, Dan, for all the assistance!

DanPatterson_Retired

engineers??? cool! use the base 9 thing.. that will keep them going for a few hours

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.