Data sources in the operation view

Data sources are used to build widgets in the operation view. They can be a variety of items, including layers in map widgets, selections in a map or list widget, or services not drawn on the map. Data must be hosted on ArcGIS Online, Portal for ArcGIS, or ArcGIS 10.1 for Server or later to use as a data source in Operations Dashboard for ArcGIS.

A map widget is often the primary data provider for the operation view, and map layers serve as a data source for other widgets. For example, your map widget might contain damage reports and evacuation shelter occupancy levels following an earthquake, which can then display in a chart or gauge widget.

Maps used in the operation view are authored and saved in your ArcGIS organizational account. These maps can contain one or more layers. When you add a map widget to the operation view, you can set options for the map's layers, including the individual layers that serve as data sources for other widgets and whether the features are selectable. You can also create a filter with a query to create a data source that only includes a certain set of features from the layer and is usable by other widgets.

If you attempt to remove a data source used by one or more widgets, a prompt appears with a list of dependent widgets that disconnect if you continue with the removal. For example, if you have a gauge and chart widget that use data sources from a map widget, the gauge and chart widgets have no data source defined (and, therefore, stop functioning) if you remove the map widget from the operation view.

If the connection to a server or data source is lost, an indication appears in the widget window alerting you of the problem.

Dynamic and static data sources

Some of your data may be static and not frequently changing, while other data is dynamic and updates periodically. For example, the locations of field crews collecting information about earthquake damage are constantly changing, while evacuation shelter locations rarely update. In this case, specify that the field crew layer refreshes at a certain interval to show the latest position and status information, while leaving the evacuation shelter layer static. Depending on how often the mapped features update, the refresh frequency could be shorter or longer to maximize the timeliness of the underlying data. For certain data, such as moving vehicles, the refresh interval is often set in minutes. With data that changes or is monitored less often, you may not need to request an update for several hours.

The refresh interval of a layer sets how frequently the operation view queries for changes, and all widgets that use the data update their contents with the newest information. The refresh interval for each layer is authored as a part of authoring your map. By default, the operation view honors the refresh intervals set in the map and sets layers with no refresh interval to static. When you configure the map widget, the data source settings indicate whether the layer is static or dynamic, and if dynamic, the refresh interval time is shown.

When editing the operation view, you can override the refresh interval on each layer in the map with a single refresh interval for all dynamic layers. To specify a single refresh interval, go to the Widgets menu and click Refresh Settings. Set the refresh type to use a single interval to update data sources, and specify a refresh interval. When using a single refresh interval, you can also override for each layer whether it is static or dynamic.

When you map population or demographics data, for example, the underlying features do not update on a regular basis. These data sources are essentially static, rather than dynamic, so you do not need to specify that they should refresh at an interval. Within the operation view, you can have a mix of dynamic and static data sources.

Regardless of the data source defined as dynamic or static, the map always presents current information when panning or zooming. For example, if you pan the map, which sends a request to the server, any changes to the underlying data reflect in the map.

External data sources

An external data source serves as input data for a widget but does not display on the map. A hosted feature layer, a map service, a feature service, or a stand-alone table can be an external data source. To include an external data source, click Edit and Edit Operation View to modify the operation view, and then click Widget and External Data Sources. You can add a layer by browsing to it in your organization, or by entering the URL to the server or a particular layer. If you specify a server's URL, choose the layers to use as data sources within the operation view. You can check one or all layers. You can add a stand-alone table by entering the URL to the particular table, for example, http://sampleserver5.arcgisonline.com/arcgis/rest/services/ServiceRequest/MapServer/1.

For each data source, specify if it contains dynamic data that refreshes periodically or remains static. In addition, you can set a filter to include only the features that satisfy a query. Use the buttons on the dialog box to set the filter, include all features again, and edit the definition.

Supported data types

Not all data types can be used as a data source. If you want your data to be accessible by other widgets, it has to be one of the following types:

Other data types from your map will be visible; however, you won't be able to use them as a data source for other widgets. The following data types will be visible on maps included in operation views:

  • ArcGIS Server feature services
  • ArcGIS Server map services
  • ArcGIS Server imagery services
  • Feature layers hosted on ArcGIS Online or Portal for ArcGIS
  • Tile layers hosted on ArcGIS Online or Portal for ArcGIS
  • GeoRSS web feeds
  • Files imported into ArcGIS Online or Portal for ArcGIS (including GPX, CSV, and shapefiles)
  • Referenced CSV files
  • Referenced feature collections
  • WMS data
  • Tile layers