Select to view content in your preferred language

Filter Options in Feature Class to Geodatabase GP Tool

592
11
11-05-2025 08:34 AM
Status: Open
Labels (1)
Ed_
by MVP Regular Contributor
MVP Regular Contributor

It would be helpful to have filter and sort options while importing a feature class/shapefile to a geodatabase similar to how you can do it in the Export Features tool.

Ed__0-1762360466224.png

 

Tags (1)
11 Comments
DuncanHornby

That wont make much sense if you are importing multiple shapefiles in one hit which are from different folders with different schemas. Why not just use the Export Features tool as you show as a way of importing into a geodatabase?

Ed_
by MVP Regular Contributor
There is a stand-alone import feature class too and you can make import feature classes tool dynamic to address what you mentioned.
DuncanHornby

What is this stand alone import tool? Can you provide a link to it?

Ed_
by MVP Regular Contributor

Sorry my mistake that's for exporting a single feature class or multiple you have the options separately. 

 

Anyways to your earlier point you can make the import feature class tool dynamic when importing more than one feature class or table 

SSWoodward
Status changed to: Needs Clarification

Can you share the specific tool you are using to import that you are requesting an enhancement for?  

Ed_
by MVP Regular Contributor

@SSWoodward It's for Feature Class to Geodatabase tool

Ed__0-1763143832773.pngEd__1-1763143853233.png

 

 

SSWoodward
Status changed to: Open
 
SSWoodward

What I'm gleaning from this is that you want the same field map, filter, and sort functionality that is available in Export Features to be present in the tool that is opened from the `import` right-click context menu of a geodatabase. 

An 'Import Features` type of option instead of just the existing `Import Feature Class` type option.  Is that correct?

Ed_
by MVP Regular Contributor

What I'm gleaning from this is that you want the same field map, filter, and sort functionality that is available in Export Features to be present in the tool that is opened from the `import` right-click context menu of a geodatabase. 

 

Yes that is correct 

 

Because, there are a lot of times when you are importing feature classes, shapefiles and even tables, where you just want to bring in part of the dataset not the whole thing, so having the same field map, filter, and sort functionality that is available in Export Features would be really helpful and save time.

SSWoodward

Makes sense.  I have relabeled this to geoprocessing since this is a GP related Idea. 

For more granular control of the data you are ingesting, the suggested workflow is to export the desired features from the class using Export Features, rather than try and import from the context menus of the destination workspace.