QUERY

Used in

Servers

Image Query Feature Extract

Parent elements

Syntax

<QUERY	Attribute Description Table
*(r)where="string"* accuracy="Distance between points" [0] featurelimit="integer" [All that meet criteria] joinexpression="string" jointables="string" subfields="#ALL# \| #ID# \| #SHAPE# \| Other fields in database" [#ALL#] > When parent element is GET_FEATURES: <BUFFER... /> <FEATURECOORDSYS... /> When parent element is LAYER and LAYERDEF in GET_IMAGE: <BUFFER... /> </QUERY >
(r): Attribute or child element is required.

Description

Defines the where clause for a stored query.
Defines attribute queries on a dataset.

Restrictions

A where statement is required for all stored queries and when joining ArcSDE tables. Otherwise, where is optional.

Notes

For information on joining tables and setting up query clauses, see SPATIALQUERY. QUERY handles only attributes, while SPATIALQUERY handles both attribute and spatial queries. It is recommended that you use SPATIALQUERY for all query statements with the exception of stored queries.
QUERY must be used when setting up a stored query.
Joined tables cannot be used with a QUERY in STOREDQUERY.
When ArcSDE is used, the subfields attribute has the full long format of the field names (e.g., MD.GDT_STATE.AREA). For shapefiles, the subfields attribute contains the field names in short format (e.g., AREA).
In a stored query, only one variable can be used.
Some symbols must be "escaped" inside a where expression:

      ampersand (&) is escaped to &
      double quotes (") are escaped to "
      single quotes (') are escaped to '
      greater than (>) is escaped to >
      less than (<) is escaped to <
The following operators work in a where clause: =, >, >=, <, <=, <>, LIKE, BETWEEN, IN, NOT IN. The following are not valid: ORDER BY and DISTINCT.

Querying with dates. The syntax for querying dates is the same regardless of the locale. A date query uses the following syntax:

{ts 'YYYY-MM-DD hh:mi:ss'}

where

YYYY	Year	Required	Use four digits for the year.
MM	Month (01-12)	Required	Use two digits for the month. March is 03.
DD	Day (01-31)	Required	Use two digits for the day. The fourth is 04.
hh	Hour (00-23)	Optional	Use a 24-hour clock. 8 a.m. is 08, and 8 p.m. is 20.
mi	Minutes (00-59)	Optional	Use two digits for the minutes. If minutes is used, hours must also be included.
ss	Seconds (00-59)	Optional	Use two digits for the seconds. If seconds is used, hours and minutes must also be included.

The year, month, and day are each separated by a dash (-). The hour, minutes, and seconds are each separated by a colon (:). The date is enclosed in single quotes (') inside curly brackets ({}). Before the date, ts (for time stamp) must be included.

For 8:03:23 a.m. January 4, 2000, the query on a DBF file looks like:

For 9:18 p.m. March 8, 2002, the query on an ArcSDE layer looks like:

Attribute Descriptions for QUERY

Attribute	Usage
accuracy	Within a feature, generalizes points based on the distance specified and the resolution of the image.
featurelimit	Maximum number of features to be extracted that meet criteria.
joinexpression	Used for join tables with DBF files only; jointables must be filled to contain list of tables used; not required when a jointable is done on ArcSDE. String must form expression: "To=[master table column which will be used for joining], From=[defines a join table column which will be joined], Type=[exact or scan]".
jointables	List of joined table names separated by blank spaces; for ArcSDE, table name is full name including database name (e.g., DATA.STATE); for shapefiles, names of DBF files without extension (e.g., STATES).
subfields	List of fields to be extracted separated by blank space. In stored queries, all fields in the layer table must be included. Performance is generally better if the field names are all upper case.
where	Defines 'where' part of SQL expression. Required when jointables attribute for ArcSDE tables is used.

Examples for QUERY

Example 1: When in a map configuration file using a STOREDQUERY. For additional examples on querying datasets in map configuration files and requests, see SPATIALQUERY.

<?xml version="1.0" encoding="UTF-8"?>
<ARCXML version="1.1">
  <CONFIG>
    <ENVIRONMENT>
      <LOCALE country="US" language="en" variant="" />
      <UIFONT color="0,0,0" name="Arial" size="12" style="regular" />
      <SCREEN dpi="96" />
    </ENVIRONMENT>
    <MAP>
      <PROPERTIES>
        <ENVELOPE minx="-178.21" miny="18.92" maxx="-66.96" maxy="71.41" name="Initial_Extent" />
        <MAPUNITS units="decimal_degrees" />
        <FILTERCOORDSYS id="4326" />
        <FEATURECOORDSYS id="4326"/>
      </PROPERTIES>
      <WORKSPACES>
        <SHAPEWORKSPACE name="shp_ws-0" directory="<path to USA ESRIDATA>"/>
      </WORKSPACES>
      <LAYER type="featureclass" name="CITIES" visible="true" id="2">
      <DATASET name="CITIES" type="point" workspace="shp_ws-0" />
      <SIMPLERENDERER>
        <SIMPLEMARKERSYMBOL type="square" width="5" />
      </SIMPLERENDERER>
        <EXTENSION type="StoredQuery">
        <STOREDQUERIES>
          <STOREDQUERY name="TestSt">
            <QUERY where=" ZIPL  =  '[%var%]' " subfields="#SHAPE# FNODE_ TNODE_ LPOLY_ RPOLY_ LENGTH RECNUM L_F_ADD L_T_ADD R_F_ADD R_T_ADD PREFIX NAME TYPE SUFFIX CFCC ZIPL ZIPR"/>
            <SQVAR position="0" name="[%var%]">
              <FIELD name="ZIPL" precision="0" type="12" size="5" />
            </SQVAR>
          </STOREDQUERY>
        </STOREDQUERIES>
        </EXTENSION>
      </LAYER>
    </MAP>
  </CONFIG>
</ARCXML>