Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I created four large polygon feature classes of surface slope classes from a grid of 6-foot cells covering half my county. In order to repair the geometry and eliminate small polygons I broke four polygon feature classes into 115 polygon feature classes.

Now I'd like to remove small polygons from each of these polygon feature classes because the small bits take up a lot of memory and aren't important at the scale of analyses I'll be doing.

I tried using ModelBuilder with a Feature Class Iterator to go through the polygon feature classes, but I could not figure out how to select the small polygons in the active feature class. In order to use the Eliminate tool, there has to be a selection of features to eliminate. The problem is there does not seem to be a way to use the iterator variable as an input to the Select by Attribute tool.

I'd sure appreciate if someone could point me in the right direction to get this process automated.

[Using ArcGIS 10.1 ArcInfo license on 64-bit Windows 7 workstation]

share|improve this question
add comment

1 Answer 1

up vote 2 down vote accepted

You need to feed the output of the iterator (green blob) into a make featurelayer tool which would then feed into your selectbyattribute tool.

share|improve this answer
    
Ok. Thank you! I was able to build a valid model using Make Feature Layer. When the model ran, however, the iterator did not seem to work. The model repeatedly did its operations on the first feature class in the dataset. I had to abort it. I did not have this problem using the iterator for Repair Geometry. Is there something else needed to close the iterator loop? –  Scott Sep 16 '13 at 16:19
    
I closed ArcMap and ArcCatalog, and reopened ArcMap. Then I rebuilt the model with Make Feature Layer, Select by Attribute, and Eliminate. It is working this time, iterating through the feature classes in the dataset. The only thing I know I did differently this time, is that I did not try to give the output feature class the same name as the input. I had thought that putting the output into a different dataset would allow me to use the same name. That wasn't the case. It threw an error because it couldn't write the output. I'm not sure if that caused the problem, but now the model works. –  Scott Sep 16 '13 at 16:51
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.