COORDS

Used in

CONFIG REQUEST RESPONSE

Servers

Image Query Feature Extract

Parent elements

HOLE MULTIPOINT PATH RING

Syntax

<COORDS >
No Attributes

No Child Elements
</COORDS >

Description

Provides a compact way to represent points for features.

Notes

The separators between the x,y coordinates and the coordinate pairs can be changed. The default separator between two coordinates is a space, and the default separator between coordinate pairs is a semicolon (;). For more information see SEPARATORS.
COORDS uses a compact method for listing the x,y coordinate pairs of a feature in the format of
    <RING>
        <COORDS> x1 x2;y1 y2;...xn yn </COORDS>
    </RING>

The equivalent noncompact method of listing x,y coordinate pairs is to use the POINT element as follows:
    <RING>
      <POINT x="x1" y="y1" />
      <POINT x="x2" y="y2" />
      <POINT x="xn" y="yn" />
    </RING>
Using COORDS means the geometry requires less bandwidth by the request or response. However, performance may be better for a large number of coordinate pairs when the non-compact format is used even though the requests and responses are longer. This is especially true when geometry is written to an acetate layer.
For the different options of representing geometry in an acetate layer, see OBJECT.

Examples for COORDS

Example 1: Used to define a spatial filter in CONFIG or REQUEST.

<?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="-180.0" miny="-152.9" maxx="180.0" maxy="153.0" />
        <MAPUNITS units="decimal_degrees" />
        <FILTERCOORDSYS id="4326" />
        <FEATURECOORDSYS id="4326"/>
        <LEGEND title="Legend" />
      </PROPERTIES>
      <WORKSPACES>
        <SHAPEWORKSPACE name="shp_ws-0" directory="<path to WORLD ESRIDATA>"/>
      </WORKSPACES>
      <LAYER type="featureclass" name="Cities" visible="true" id="0">
        <DATASET name="cities" type="point" workspace="shp_ws-0" />
        <SPATIALQUERY>
          <SPATIALFILTER relation="area_intersection">
            <POLYGON>
              <RING>
                <COORDS>-133.15 78.07;-131.09 74.70;-128.10 76.38;-128.10 76.38;-133.15 78.07</COORDS>
              </RING>
            </POLYGON>
        </SPATIALFILTER>
        </SPATIALQUERY>
        <SIMPLERENDERER>
          <TRUETYPEMARKERSYMBOL transparency="0.5" glowing="0,255,255" shadow="0,0,0" font="ESRI Cartography" character="252" fontcolor="255,255,0" fontsize="16" angle="90" />
        </SIMPLERENDERER>
      </LAYER>
    </MAP>
  </CONFIG>
</ARCXML>

Example 2: When using COORDS in an acetate layer.

<?xml version="1.0" encoding="UTF-8" ?>
<ARCXML version="1.1">
  <REQUEST>
    <GET_IMAGE>
      <PROPERTIES>
        <ENVELOPE minx="-180.0" miny="-90.0" maxx="180.0" maxy="90.0" />
        <IMAGESIZE width="800" height="600" />
      </PROPERTIES>
      <LAYER type="acetate" name="Selectedmark" id="acetate">
        <OBJECT units="database">
          <SIMPLELINESYMBOL color="0,0,0" width="6" />
          <POLYLINE>
            <PATH>
              <COORDS>-2.1079549837513 19.99815142335011;28.99468788980437 15.88488432940315;55.99468788980437 35.88488432940315 </COORDS>
            </PATH>
          </POLYLINE>
        </OBJECT>
      </LAYER>
    </GET_IMAGE>
  </REQUEST>
</ARCXML>

Example 3: When in a FEATURES response.

<?xml version="1.0" encoding="UTF8"?>
<ARCXML version="1.1">
<RESPONSE>
  <FEATURES>
    <FEATURE>
      <ENVELOPE minx="-89.04" miny="15.91" maxx="-87.90" maxy="18.51"/>
      <FIELDS AREA="8543.292" NAME="Belize" ABBREVNAME="Belize" FIPS_CODE="BH"   SHAPE ="[Geometry]" ID ="105" />
      <POLYGON>
        <RING>
          <COORDS>-88.11 18.51;-88.19 18.32;-87.92 18.40;-87.90 ...-88.11 18.51</COORDS>
        </RING>
      </POLYGON>
    </FEATURE>
    <FEATURECOUNT count="1" hasmore="false" />
  </FEATURES>
</RESPONSE>
</ARCXML>