Layers, Labels, and Symbols

The symbology choices you make in ArcMap are seen by all end users in Wavepoint. For example, notice the layer names, the symbols, the layer order, and the labels of the fiber facilities on this map in ArcMap:

And notice all the same layer and symbology choices are seen in the published map service in Wavepoint:

Thus, think about the look and feel of the map that benefits Wavepoint users. After all, the choices you make regarding symbology, labeling, and draw scales are seen and used every day. With a new implementation, consider having a feedback forum for your users to offer ideas to make the map easier to use. With their feedback, you can re-publish the map service to improve their efficiency.

While making the underlying map, keep the following in mind:

Layers

• Layer Order

  • Use the Table of Contents in ArcMap to control which layers appear on top and which appear on bottom in the published map service. Just like any map, typically point features are the top-most layers, followed by lines, and then followed by polygons.

• Layer Names

  • The layer names you see in the Table of Contents are the same names you see in the published service. To rename a layer, click it once to highlight in blue, then press F2. Type a new name, then press Enter.

• Layer Groups

  • You can group layers in the Table of Contents. For example, in the first image above, the layers are in a Fiber Data group, and that same Fiber Data group acts as a header in the Wavepoint legend. However, Wavepoint does not support collapsing layers in the legend. In other words, groups do not hurt anything, but they are not functional in the application.

• Layer Visibility

  • We recommend not drawing all layers at all scales. For example, it is not valuable to see all splice cases at a municipality-wide scale. Instead, set splice cases to draw once zoomed in at a reasonable scale.

• Prohibited Layer Types

  • A published service cannot include graphic layers. If you attempt to publish a service with these kinds of layers, they produce a descriptive error stating they are not allowed, and you need to remove them prior to publishing the service.

• Other Considerations

  • Ensure that each feature class is only included once in the Table of Contents.

  • Ensure there are no definition queries written against any layer. Wavepoint’s access to the underlying fiber data is only through this published service, and a definition query could prevent the application from attaining necessary data

Symbology

• Feature Class Symbols

  • The published service supports symbol configurations made through the standard Layer Properties > Symbology dialog.

• Subtype Symbols

  • The published service supports subtype symbols.

• Transparency

  • The published service supports transparency. For example, you can include parcels or building footprints for reference and make them 50% transparent.

Labels

• The published service supports label configurations made through the standard Layer Properties > Labels dialog. This includes colors, fonts, styles, and standard label expressions (for example, to concatenate multiple fields from the same data table).

• Much like layer visibility, we recommend not labeling feature classes at all scales. Instead, have labels turn on at appropriate scales.