What's New in ArcXML 1.1 for ArcIMS 9.1

The following changes have been made to ArcXML 1.1 for ArcIMS 9.1.

Modifications to support dynamic queries

When using Image Services, dynamic layers can be queried when making a GET_FEATURES request. This functionality is not valid with ArcMap Image or Feature Services.

• GET_FEATURES
  • WORKSPACES is a valid child element.
• LAYER, TARGETLAYER
  • DATASET is a valid child element in a GET_FEATURES request.
• MAP
  • dynamicfeature is a new attribute.
• TARGETLAYER
  • type is a new attribute.
• A section on how to create dynamic queries has been added to Using GET_FEATURES and FEATURES.

Modifications for Metadata Service elements

• SEARCH_METADATA
  • The list of child elements has been modified depending on whether the search criteria is nested or not. Search criteria must be added in a specific order. See the Notes section for more details.

Changes to attribute names and values:

• SCALEBAR
• texttransparency is the correct attribute name. In previous versions of ArcIMS, the attribute was listed as textransparency.
• RASTERMARKERSYMBOL
• The default value for usecentroid has been corrected. The value is now "false".
• SIMPLEMARKERSYMBOL
• For Feature Services, the default value for usecentroid has been corrected. The default value for Feature Services is "false" and for Image Services is "true".
• TRUETYPEMARKERSYMBOL
• The default value for usecentroid has been corrected. The value is now "false".
• FIELD
• The values of 13 (CLOB_TYPE), 14 (NVARCHAR), and 15 (NCLOB_TYPE) have been added to type.
• SIMPLELABELRENDERER, VALUEMAPLABELRENDERER
• The values for linelabelposition have been changed to all lower case.

Other items of note

• The ArcXML Guide no longer has a pdf version.
• When using direct connect, SDEWORKSPACE server must have a value even though other ESRI products may not have this requirement.
• FEATURECOORDSYS and FILTERCOORDSYS should always be included in a map configuration file. Many clients, including ArcMap and WMS clients, may not handle projections correctly if this information is not included in the service.
• COORDSYS should be used for all image layers in a map configuration file. If an image layer is missing in a response, check if COORDSYS is included in the map configuration file.