Description:

Requests features as a compressed binary stream from the Feature Server or requests attribute data in ArcXML format from the Query or ArcMap Servers.

Restrictions:

• Can only be used on one layer at a time. Layer must exist in the ArcIMS service.
• Either SPATIALQUERY or QUERY is required.
• Skipfeatures is valid only when outputmode is set to "xml" or "newxml".
• The attribute dataframe is valid only with the ArcMap Server.

Notes:

• See EXTRACT for response.
• A GET_FEATURES request to an Image Service gets routed to the Query Server. This routing information is contained in the URL sent to the ArcIMS site such as in the following example (all one line):
  http://myComputer.domain.com/servlet/com.esri.esrimap.Esrimap?ClientVersion=9.0
          &ServiceName=myservice
          &CustomService=Query
          &Form=True&Encode=True
  
  Requests to an ArcMap Image Service do not need to be rerouted.
  
  
• The attributes beginrecord and featurelimit are used together to limit the number of features returned. Featurelimit is used to set the number of features returned. Beginrecord is used to start the retrieval at a specified record. For example, if 25 features should be returned, featurelimit is set to "25". For the first retrieval, beginrecord starts at "0" (the default). For the second retrieval, beginrecord should start at "25". To determine whether more than 25 features were extracted, the attribute hasmore in the FEATURES response will be set to "true" (more records) or "false" (no more records).
• Outputmode defines whether the data is streamed to the client or sent to the client in ArcXML format. If outputmode is binary, then the request goes to the Feature Server and the response is a compressed binary stream. This is the default and is valid only for Feature Services. To return data in ArcXML format, outputmode can have one of two values: newxml or xml.
  
  If outputmode="xml", then all features are returned in a short ArcXML format using the FIELDS element. This format is not valid for use with the ArcXML DTD:
  <FIELDS CUST_ID="4" NAME="Customer" #SHAPE#="[Geometry]" #ID#="3" />
  
  If outputmode="newxml" then all fields are returned in a longer ArcXML format in the FIELD element. This format can be used with the ArcXML DTD:
  <FIELDS>
    <FIELD name="CUST_ID" value="4" />
    <FIELD name="NAME" value="Customer" />
    <FIELD name="#SHAPE#" value="[Geometry]" />
    <FIELD name="#ID#" value="3" />
  </FIELDS>
• Compact can be used to switch the geometry used in the output ArcXML to a shortened format. When compact is true, the response uses the COORDS element:
  <MULTIPOINT>
    <COORDS>-122.406680 37.747422;-123,500555 37.820000</COORDS>
  </MULTIPOINT>
  
  When compact is false, the response uses the POINT element:
  <MULTIPOINT>
    <POINT x=-122.406680 y=37.747422 />
    <POINT x=-123,500555 y=37.820000 />
  </MULTIPOINT>
  
  Setting compact to "true" means the geometry requires less bandwidth by the request or response. However, performance may be better when compact="false", even though the requests and responses are longer.
• Two methods can be used to retrieve the number of selected features without returning FEATURE elements:
  • To get the total number of seclected features but not a global envelope, you can use GET_FEATURES skipfeatures="true". In the FEATURES response, only FEATURECOUNT is returned. You can include a global envelope by setting both GET_FEATURES skipfeatures and globalenvelope to "true".
  • To get the total number of selected features and a corresponding global envelope, you can use the following combination of attributes in GET_FEATURES:
    • attributes="false"
    • geometry="false"
    • envelope="false"
    • globalenvelope = "true"
    When attributes, geometry, and envelope are set to "false", only FEATURECOUNT is returned. If globalenvelope is set to "true", the global envelope is included using ENVELOPE. If globalenvelope is set to "false", no ENVELOPE is returned. If at least one attribute among attributes, geometry, and envelope is set to "true", FEATURE elements are returned.
• For more details on using GET_FEATURES and FEATURES, including additional examples, see Using GET_FEATURES and FEATURES.

Attribute Descriptions for GET_FEATURES:

Examples for GET_FEATURES: