Skip to main content

Web Maps

OmniSpatial can load Web Maps from ArcGIS Enterprise, ArcGIS Online, or directly from a Web Map JSON file.

Authoring Web Maps​

When authoring Web Maps to be used within OmniSpatial, the following considerations should be made.

Use Feature Layers​

Layers should be added as individual Feature Layers rather than all together as Map Image Layers.

For example, instead of adding the layer as https://arcgis.rizing.dev/server/rest/services/YourService/MapServer, you would add each layer from that service as individual layers:

  • https://arcgis.rizing.dev/server/rest/services/YourService/MapServer/0
  • https://arcgis.rizing.dev/server/rest/services/YourService/MapServer/1
  • https://arcgis.rizing.dev/server/rest/services/YourService/MapServer/2
  • etc.

Choose correct server type​

When adding data to a Web Map it is important to choose the correct server type based on the desired usage of the data. If the intent is to edit data, then add the layers from a Feature Service rather than a Map Service. If the intent is only to "view" data than use a Map Service.

NOTE: when working with a service that has Linear Referencing enabled (LRSServer or LRServer extension), then always add layers from the Map Service (even if editing is desired).

Examples:

  • Map Service: https://arcgis.rizing.dev/server/rest/services/YourService/MapServer/0
  • Feature Service: https://arcgis.rizing.dev/server/rest/services/YourService/FeatureServer/0

Layer names​

Depending on how/where you create your Web Map, the authoring application may add additional unneeded information to the layer's name (a.k.a. title). As such, it is recommended to adjust your layer names to be as short and concise as possible.

For example, rename My Map Service - Street Light to Street Lights

Forms and data​

  • Add field aliases to ensure forms are readable and users understand the data that is presented to them
  • Hide unnecessary or irrelevant fields
  • Create pop-up field lists so that fields are logically grouped together

Cartography best practices​

Ensure good design principles for cartography are used when constructing Web Maps.

Examples​

  1. Ensure only the most pertinent layers, depending on the desired use, are visible by default
  2. Setting minimum zoom extents so high density data is not rendered at impractical scales
  3. Choose meaningful symbology with high contrast colors
  4. Take into account color blindness and other handicaps when choosing colors

Resources​

Web Map authoring checklist​

The following is an example checklist that could be used when authoring Web Maps:

  • Layers been added from the correct service (Map Service vs Feature Service)
  • Each layer name has been shortened and given a concise name
  • Field aliases exist so that each field is obvious and user-friendly
  • Unnecessary fields are hidden
  • Each field has a human-readable and understandable alias
  • Pop-up field lists have been created to group related fields together
  • Only pertinent layers are visible by default
  • Symbology is meaningful
  • Color provide contrast with the base map
  • Colors are color-blind friendly
  • The initial map extent is meaningful (relevant to the largest target audience)
  • Web Map has a meaningful title

For more useful tips see Esri's Create maps documentation.