Name

The OGC service type. This property is automatically populated by ArcGIS Server and should not be modified.

Title

The name of the map or image service that was used to create the WMS service. This property is automatically populated by ArcGIS Server and should not be modified.

Abstract

A narrative description that provides additional information about the WMS service. For example:

WMS service maintained by Acme Corporation. Contact: webmaster@wmt.acme.com. High-quality map showing eagle nests and possible nesting locations.

Keywords

A list of keywords or keyword phrases describing the WMS service that aid in catalog searching. For example:

map, bird, eagle, nest, site

Online Resource

The OnlineResource property lists the URL of the WMS service. It is necessary for a WMS client to communicate correctly with your WMS service. This property is automatically populated by ArcGIS Server and should not be modified.

ContactPerson

The primary contact person for the WMS service. For example:

John Smith

ContactPosition

The position of the contact person for the WMS service. For example:

IT Analyst

ContactOrganization

The organization that created the WMS service. For example:

NASA

Address type

The address type used by the organization that created the WMS service. For example:

postal

Address

The address of the organization that created the WMS service. For example:

380 New York Street

City

The city in which the organization that created the WMS service resides. For example:

Redlands

StateorProvince

The state in which the organization that created the WMS service resides. For example:

California

PostCode

The postal code in which the organization that created the WMS service resides. For example:

92373

Country

The country in which the organization that created the WMS service resides. For example:

USA

ContactVoiceTelephone

The telephone number where the primary contact person for the WMS service can be reached. For example:

+1 909 793-2853

ContactFacsimileTelephone

The fax number where the primary contact person for the WMS service can be reached. For example:

+1 123 456-7890

ContactElectronicMailAddress

The email address where the primary contact person for the WMS service can be reached. For example:

user@host.com

Fees

Text describing the fees imposed when accessing the WMS service. For example:

none

Access constraints

Text describing the restrictions and legal prerequisites for accessing and using the WMS service.

For internal use only. Do not distribute.

SLD Path or URL

SLDs allow you to publish multiple styles for each WMS layer. If you are binding an SLD file to the current WMS service, you need to enter the SLD path or URL property to the URL, UNC path, or physical location of an SLD XML file. The ArcGIS Server account must have access to the location for ArcGIS Server to properly read the SLD XML file.

To learn more about SLDs, see Using Styled Layer Descriptors with WMS services.

Additional spatial reference systems

This property can be used to add spatial reference systems to WMS services. By default, WMS services only list two spatial reference systems: EPSG:4326 (or CSR:84 for WMS 1.3.0) and the spatial reference of the map service on which the WMS is enabled.

To list additional spatial reference systems, separate the spatial reference systems with a comma (,). For example, EPSG:4267,EPSG:4269,EPSG:102113. The EPSG namespace (for example, EPSG) and the EPSG ID (for example, 4267) must be separated by a colon (:), or the spatial reference will be ignored by the server.

Custom spatial reference systems

The listCustomCRS property allows you to define a custom projection or well-known text (WKT) representation of a projection in a WMS service. This means publishers and consumers of the WMS can do the following:

• Assign IDs to custom projections and advertise them through the WMS capabilities file.
• Overwrite an existing projection with a WKT string.
• Request a map in a particular projection by directly specifying the well-known text.

Identify tolerance (pixels)

This property allows you to define a tolerance (in pixels) in which the GetFeatureInfo operation will return feature information to the client when they click the screen. For example, if you define a pixel tolerance of 10 for your WMS, the information will be returned to the client as long as they click within 10 pixels of the feature on the screen.

Use layer names from the map document

By default, this option is unchecked, meaning that layers in the WMS service will be represented with zero-based integers, indicating their position in the table of contents from the top down.

Starting at version 10.8, there are no restrictions to the characters that can be used in a layer name, and WMS server will generate a unique identifier for the name when necessary.

WMS server will assign a unique name by character substitution (replacing characters with an underscore) and by adding a numeric suffix. This will occur in the following instances:

• A map contains two or more layers with the same name.
• A layer name begins with a number.
• A layer name contains spaces or special characters, including ?,&,=,+,`,#,%,^,{},[],<>,,,|,"

Force map re-aspect based on width and height

This property determines whether the map is re-aspected. By default, this option is deselected, which means that the pixels representing the map area are stretched to fit into the height and width requested by WMS clients.

If this option is selected, the pixel height and width ratio will stay the same. When a map is requested at full extent, it may not fill the entire viewing area.

Assign a name identifier to a layer

By default, WMS services do not assign a <Name> to group layers. The namedLayersMode property allows you to control how layers in a WMS service are assigned a Name identifier. If the property is set to allLayers, a Name identifier is assigned both to group layers and to their sublayers. If it is set to subLayers or left unspecified, a Name identifier is only assigned to the sublayers of a group layer. This means clients cannot include a group layer in a GetMap request, but have to specify each individual sublayer inside the group layer.

&

&amp;

<

&lt;

>

&gt;

"

&quot;

'

&apos;