Navigation:  Command Reference Configuration > Configuration File - Setup > Folder: Tasks > Feature Query Filter

The export can be limited to certain object per task with the FeatureQueryFilter. Attention should be paid to the fact that the spelling of the queries is directly dependent on the used data source. Thus it is favorable to test these in GIS in the definition query of the Feature Class and subsequently to copy them into the configuration.

 

Example: only the objects whose attribute 'WIDCODE' has the value '22-11100' are exported

 

Syntax of the Where Clause

The type or syntax of the Where Clause depends on the underlying database. The Where Clause for a filebased Geodatabase looks different than for a personal Geodatabase. e.g. fGDB -> '  pGDB -> "

The correct spelling can be found out through the Query Builder in ArcMap.

The operators LIKE and IS DIFFERENT (<>) must be written in the configuration as follows

 

<FeatureQueryFilter Where="KGNAME LIKE'%en%'" />

 

<FeatureQueryFilter Where="Layer&lt;&gt;'VS'" />

The 'is different' query must be entered in this form only when using Notepad++ or other text editors; qualified XML editors (e.g. XML Notepad 2007) perform automatically the UTF-8 encoding when saving, i.e. the entry there must be as <>.

The entry lt;&gt; becomes in XML <FeatureQueryFilter Where="Layer&amp;lt;&amp;gt;'VS'" />  and gives for CAD export an 'Underlying DBMS error' with the error message "Around ';' was specified a non-Boolean expression in a context where a condition is expected"

 

Attention: For WhereClauses that refer to joined Feature Classes, the field names must be qualified.