Defining symbology for input feature sets

Many geoprocessing tasks use feature sets as input. When you create a feature set variable, you set a schema that defines the shape type (point, line, or polygon), the attributes you want the user to supply, and the symbology used to display the features that the user digitizes.

Feature Set schema

Learn more about feature sets

The client application is responsible for displaying the features the user digitizes. This means that the symbology you define for the feature set must be symbology that the client can display.

The topic Defining output symbology for geoprocessing tasks describes the symbology supported on all clients. Although the topic discusses output symbology, the same rules apply for input feature set symbology. These rules are summarized below.

The following layer symbologies are supported by all clients:

The table below shows the ArcMap symbol types that all clients can use. If your client is ArcMap or ArcGIS Explorer, there are additional choices. Again, see the topic Defining output symbology for geoprocessing tasks for more details.

Points

Lines

Polygons

Simple marker symbol

Simple line symbol

Simple fill symbol

Character marker symbol (see note below)

Picture fill symbol

Picture marker symbol

Symbols to use for thin clients

Character marker symbols can have multiple symbol layers, as illustrated below. Symbols with multiple layers cannot be drawn by Web clients.

Symbol layer
NoteNote:

When you apply a schema, the schema is read and stored with the data variable. If you subsequently change the schema—for example, changing the symbology or adding a coded value domain—you need to reapply the schema.

  1. In ModelBuilder, right-click the feature or record set variable and choose Properties.
  2. Click the Data Type tab.
  3. Choose the schema (dataset, layer file, or layer) again and click OK.

After changing the schema and saving the model, you must re-create the tool layer (if you are using ArcMap to publish your service) and restart the service.

Because the schema is stored with the feature or record set, you can delete the schema once it has been applied.

Related Topics


11/18/2013