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

Model Builder How to use Calculate Field for a single field with multiple values

BethAllen

In ArcPro 3.2.1, I'm trying to use the Calculate Field Tool within Model Builder to update the values of a field that has several different values. For example, the field currently contains the values of AVE, BLVD, CIR, CT, HWY etc. I want to update these values to the fully spelled out versions: AVENUE, BOULEVARD, CIRCLE, COURT etc. Is there a more efficient way to do this than selecting and calculating each value individually? This will be only one piece of a larger model and I don't want to have 30 select/calculates in the model -- it will be a mess! Thanks in advance.

Find more posts tagged with

Accepted answers

All comments

AlfredBaldenweck

There's definitely a more elegant way to do this, but I'd do like:

expandStreets(!FieldA!)

def expandStreets(field):
    field = field.replace(" AVE", "AVENUE")
    field = field.replace(" CT", " COURT")
    field = field.replace(" ST", " STREET")
    # Etc...
    return field

Note that I have a space in front of the abbreviation so you don't get Streetephen Boulevard

MErikReedAugusta

You can do this with a dictionary lookup that the Calculate Field script checks & returns. The code below is for Python, but the same thing could also be accomplished in Arcade, too.

First, you'll need to write a function in the Code Block that does the lookup:

suffixes = {'AVE':  'AVENUE',
            'BLVD': 'BOULEVARD',
            'CIR':  'CIRCLE',
            'CT':   'COURT',
            'HWY':  'HIGHWAY',
           }
def Suffix(oldValue):
  # This will replace any of the values you were prepared for with the new
  # values
  if oldValue in suffixes:
    return suffixes[oldValue]

  # And this will keep your original value unchanged, in case you didn't
  # prepare for one, otherwise the calculation will fail when it returns a
  # value it doesn't recognize.
  else:
    return oldValue

Then, in the Expression line, you just call that function:

Suffix(!FieldName!)

You still have to write out all 30 known options in that dictionary (Lines 1–6, in the example), but at least it's all contained in the one Calculate Field call.

AlfredBaldenweck

Yeah this one of the more elegant ways lol

MErikReedAugusta

It's also worth noting that your solution presumes suffixes in the same field as street names, and mine presumes suffixes in a standalone field.

In the road data I've worked with in the past, yours is probably the safer assumption, but mine was based on my reading of the OP.

@BethAllen , are your suffixes already in a standalone field, or do you have to extract them from a full street address (e.g., getting "ST" from "1521 STEPHEN ST")? Because that could significantly change how best to approach this.

BethAllen

Thanks to all for the responses.

My suffixes are already in a standalone field. Actually all of the components of the street name are already parsed into different fields but each of the components (other than the core street name) are abbreviated. I need to spell them out fully for each field.

BethAllen

Thank you for your thoughtful responses! So I decided to try your recommendation on another field first (one with fewer and simpler values) since I know nothing about coding! I'm using a street pre-directional field called "AVDIR". The only four values are N, S, E, W which I need fully spelled out. Below is what used; however when I run it fails (see third screenshot below).

AlfredBaldenweck

Two things:

You named a variable (your direction dictionary) the same as a function. That's confusing for humans and even more confusing for the computer, which is why you're getting the error.
Your dictionary should be inside your function if you want to be able to access it.

def compass(field):
    dirDict = {"N":"North"}
    #code 
    #code
    x = dirDict[field]
    return

Try changing the name and the location of the dictionary and see if that fixes it.

MErikReedAugusta

TL;DR: Line 1 and Line 7 should have different names, and Line 8 should be looking at the name from Line 1.

The issue is that you used the same name for both the function and the dictionary, and line 1 is looking at the wrong one. This one is partly on me. Python is case-sensitive, and since I tend to use Title Case for Functions and lower case for variables, I didn't notice that I'd called both a variation of "Suffix" in my examples, which could potentially be confusing.

Since Python is case-sensitive, you could just capitalize one of them like this, and it would work (note the lowercase on line 1 and line 4, compared to the uppercase on line 3):

compass = {'N': 'NORTH', ...}

def Compass(oldValue):
  if oldValue in compass

But it's probably better to get in the habit of being more explicitly different, for safety & clarity:

compassDict = {'N': 'North', ...}

def CompassFunc(oldValue):
  if oldValue in compassDict:

BethAllen

I just can't get it to work. My problem is I don't know anything about code so it's like I'm trying to read before learning the alphabet. I do appreciate all the help!

AlfredBaldenweck

Can you post another screenshot or sample again? Also, a screenshot of your table would help.

Truth be told, I find Python Field Calculator much more confusing than the Arcade one, but here's a rough explanation of how it works.

The "AVDIR =" block is there for you to put in a value. That could be a static value ADVIR =2 or it can be a dynamic one based off of one or more functions, which is what we're doing now ADVIR = myfunc(!FieldA!)

A function is a set of steps you define to accomplish a goal of yours. They are used to avoid having to retype your code a billion times, and we write them out in the code block. The code block can contain multiple functions, depending on your needs.

Functions are defined using the pattern def functionName(parameter1, parameter2...): and end with a return statement, which tells the computer that 1) the function is done and 2) whether or not it needs to send a value back to whatever called the function in the first place. Some functions do not take any parameter, some take 20. It just depends on your needs.

For example, we could make a function to make a peanut butter sandwich. We feed the function peanut butter, bread, and a knife, and we get a sandwich out of it.

# Define your function
def pbSandwich(peanutButter, bread, knife):
    sandwich = 1 slice of bread # start with one piec
    knife = knife+ peanutButter # put the peanut butter on the knife
    sandwich = sandwich + knife # put the spread on the bread
    sandwich = sandwich + 1 slice of bread # close the sandwich
    return sandwich

# Call your function
lunch = pbSandwich(peanutButter, bread, knife)

There's more context missing in this code (what is a knife? how did we get it?) but the important part is that we have instructions telling us how to make a sandwich whenever we have the right ingredients.

Applying that to the field calculator and the code we've given you,

def expandStreets(streetSuf):
    suffixes = {'AVE':  'AVENUE',
            'BLVD': 'BOULEVARD',
            'CIR':  'CIRCLE',
            'CT':   'COURT',
            'HWY':  'HIGHWAY',
           }
    # Find me the matching suffix for what I feed it. 
    # If it's not in the list, just give me what I already have
    # So if streetSuf == 'AVE', I get 'AVENUE', but 
    # if it equals 'PL', I just get 'PL' since it isn't in the dictionary
    expnd = suffixes.get(streetSuf, streetSuf) 
    return expnd

And then we use the AVDIR = block to feed it the value for each record in your table of a given field. Not sure of the reason the syntax is !FieldA!, but that's how it's set up, so that's what we're doing.

Anyway, please share your errors and we'll figure it out together

BethAllen

So below is a partial screenshot of my table with the field AVDIR highlighted. I decided to start on this field since it has fewer values (only 4 - N, S, E, W) which I need fully spelled out (NORTH, SOUTH ETC). Below that is what I currently have in the Code Block which is all wrong; I know. Your explanation/analogy is great, I'm just not sure how to apply it.

AlfredBaldenweck

Goes back to the earlier issue of calling the dictionary and the function the same thing.

You want to return compassDict[oldValue]

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.