O V E R V I E W
A geometry service contains utility methods which provide access to sophisticated and frequently used geometric operations. An ArcGIS Server Web site can only expose one Geometry service with the static name "Geometry". Note that geometry input and output, where required, is always packaged as an array.
Use a geometry service to:
Buffer, densify, project, relate, and simplify geometry
Calculate areas, lengths, and label points for geometry
Return well known ids and text strings for spatial references and units
WSDL syntax
http://<Web Server Hostname>/<ArcGIS Instance>/services/Geometry/GeometryServer?wsdl
Working with a geometry service
Geometry service methods typically take as input a spatial reference (SR)
and an array of geometries assumed to be in that spatial SR. This
SR cannot be null. This allows callers to avoid
duplicating the spatial reference within each geometry in the array. The
geometry returned from a method call is not associated with a SR. It
is the consumers responsibility to
associate the returned geometries with the correct SR.
Finding a Well-Known ID
Working with a geometry service often involves defining a spatial reference,
transformation, and/or unit. The International
Association of Oil & Gas Producers (OGP) maintains a set of internationally
recognized numeric codes to identify standard spatial references (coordinate
systems), datum transformations, and linear and angular units of measure.
The codes are termed EPSG codes or "factory
codes" from the now-defunct European Petroleum and Survey Group which
was absorbed into the OGP. ESRI has also
defined a set of unique numeric codes to identify the same or similar
geometric entities. Other authorities and groups
can define their own unique numeric codes as well. In
order to accommodate multiple authorities without overlapping codes, the
geometry service uses an explicitly defined range of codes for known and
unknown (custom) authorities. The codes are designed
to identify an commonly recognized geometric entity, thus each code is
termed a "well-known id". Here are the current rules for mapping WKID ranges
to default authority names used by a geometry service:
EPSG codes map to the WKID code range 1000 - 32768. EPSG version: 6.12
ESRI codes map to the WKID code range 33000 - 199999. Current ESRI PE (projection engine) library version: 9.3
Custom codes map to the WKID code range 200000 - 209199.
WKIDs for the EPSG and ESRI authorities are
available for the following entities:
Spatial Reference - Geographic Coordinate Systems
Type
Type3
Spatial Reference - Planar (Projected) Coordinate Systems
Type
Type4
Datum Transformations
Units
Type
Methods
|
Proxy method |
Description |
|
Buffers an array of geometries by each distance specified in an array of distances.
| |
|
Converts non-linear geometry to linear geometry.
Adds vertices to linear geometry. | |
|
Defines a spatial reference based upon its well known identifier (WKID) and optionally a WKID for a vertical datum.
| |
|
Defines a spatial reference based upon its well known text string (WKT) and optionally a WKT for a vertical datum.
| |
|
Finds a predefined linear or angular unit of measure based on its EPSG or ESRI WKID.
| |
|
Finds a predefined linear or angular unit of measure based on its EPSG definition string.
| |
|
Calculates area and perimeter length for each polygon.
| |
|
Calculates points for label placement inside each input polygon.
| |
|
Calculates length for each input polyline.
| |
|
Projects an array of geometries from their current spatial reference to a destination spatial reference.
| |
|
Determines the pairs of geometries from the input geometry arrays that participate in the specified spatial relation.
| |
|
Generates topologically correct geometry.
|