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

Use a Definition Query in a Model

BarryFosberg

I am using ArcPro 2.8.

1. In a model, can run a definition query?

2. If yes, Is there any advantage in a model to using a definition query over just adding a Select tool?

The examples I have tend to be a matter of one or more select by attribute statements which would be the same in either a definition query or a Select By tool.

Find more posts tagged with

Accepted answers

JonathanNeal

@BarryFosberg You will first set up your definition query in the Map layer. Then the tools that are ran within ModelBuilder will honor them. Any tool that operates against the map layer will check selected and definition queries. Note if you run Copy Features against the data on disk, it will not check definition queryies or selections.

All comments

BarryFosberg

And thank you also.

The advice about how selects and DQ interact is subtle and important. Worth the thread by themselves.

I had been using , without knowing it, this solution. Part of my immediate problem is that I need the original data to be geo-located, then divided into 6 sub tables. I was hoping it would be more elegant to DQ this within the model. As of now I have copy's in the Map Layer each with itsown DQ. I think that can be cleaned up using an iterator. Next I will be learning about iterators.

JonathanNeal

BarryFosberg

Thanks for the fast reply.

What started the quest was tiring to figure out how to put a definition query into a model. Definition query were not listing as a geoprocessing tool and copy feature did not have a place to enter a definition query.

How do you place the DQ into the model?

JonathanNeal

@BarryFosberg How all tools think of definition queries and selections are the same. There is no advantage to using one over the other. Some of the ModelBuilder iterators use definition queries to perform their functions. But, for triva night, there is a Gotcha you can find yourself in that you may consider.

Definition Query + Selection != Selection + Definition Query

That is, if you do a selection first, that has elements that your definition query would have excluded, the tool will still act on those elements. The result the tool will act on will be all elements that qualify in the selection and all elements that qualify in the definition query.

But, if you did the Definition query first, and the selection second, it will be the result will be the intersection of both filters.

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.