About creating Runtime content

You can consolidate the features, tabular data, basemaps, network datasets, and locators from your map into a folder and prepare it for use in applications built with ArcGIS Runtime SDKs. This folder can then be provisioned to devices to use with applications that run offline (applications that can run disconnected from ArcGIS Server or ArcGIS Online). For more information on building applications with ArcGIS Runtime SDKs, see the developers site.

Data from feature services and map services cannot be used. For more information on using services in your ArcGIS Runtime SDKs, see Services pattern.

Before you can create Runtime content, the Share As menu item must be enabled in ArcMap Options.

To enable the Share As Runtime content menu item

1. Open ArcMap.
2. In the ArcMap main menu, click Customize > ArcMap Options.
3. In the ArcMap Options dialog box, click Sharing.
4. Check the Enable ArcGIS Runtime Tools check box and click OK.

To create Runtime content

1. Open ArcMap.
2. Open or create a map document with the desired data.
3. In the ArcMap main menu, click File > Share As > Runtime content.

   In the left pane of the dialog box that appears, you can access settings (options) for consolidating your data. For more information, see the option descriptions that follow.

4. When you're finished specifying settings, click Share.
5. ArcMap outputs your package to the folder you specified in the Output folder setting.

Option descriptions

Output folder

Runtime content is saved locally into the folder you specify here. This folder can be deployed to your devices to use with your ArcGIS Runtime-based applications.

Feature and Tabular Data

You can use feature and tabular data from the current map as operational layers in your Runtime applications. These layers can be used to view and query the data contained in them.

Note:

When layers are consolidated, they will all be reprojected to the spatial reference of the map's data frame or to the spatial reference of the basemap's tiling scheme, if a basemap is included.

For feature and tabular data to be included in the Runtime content, there are a few restrictions to keep in mind:

• Only feature layers, tables, and relationship classes are supported.
• If a feature layer references or participates in a relationship class that references unsupported data, the layer will not be included in the Runtime content.
• All of the layers in the current map must come from the same workspace.

The following options are available for features and tabular data:

• Include feature and tabular data for read-only reference—Include all of the feature layers, tables, and relationship classes from the current map in the Runtime content. These layers will be read-only in your ArcGIS Runtime SDK-based application. If the Optimize size for view-only option is selected, the layer will be optimized for size and will be suitable for viewing only in your ArcGIS Runtime SDK-based application. For these layers
  • All fields not used for rendering and labeling are removed.
  • The precision of their spatial reference is set to 0.1 meters.
  • They are not suitable for use with a network dataset.
• Do not include feature and tabular data—Do not include any of the features or tabular data from the current map in the Runtime content.

Basemap

If your map contains a basemap layer, you can include it in the Runtime content. Basemap layers will be used to create tile caches, a set of premade tiles suitable to use as basemaps in your Runtime applications. Tile caches typically display more quickly than other basemaps. Selecting this option increases the size of the content and the time it takes the content to be created. You can adjust tiling scheme and other settings to accommodate the balance for the level of detail and performance you want. For more information, see About tile packages.

Note:

If the data you need to show as your basemap must be queryable, selecting this option is not appropriate.

Note:

If you are including features, they're reprojected to the spatial reference of the tiling scheme.

The following options are available:

• Use a basemap layer from the current map—Creates a tile cache from the selected basemap layer in the current map and includes it in the Runtime content.
• Do not include a basemap—Do not include a basemap in the Runtime content.

Network Data

If your map contains a network dataset or a network analysis layer that references a network dataset, you can include the network dataset in your Runtime content as a transportation network for routing and driving directions. When including a network, all feature layers the network references become part of the Runtime content. This may include layers that are not part of the map. For example, if you only have a network layer in the map, your Runtime content includes the streets, junctions, and turns feature classes associated with the network.

For a network dataset to become a transportation network, there are a few restrictions to keep in mind:

• The network dataset must be part of a geodatabase. This excludes networks that are in SDC or shapefile format.
• The network dataset must be from ArcGIS 10.0 or later. If your network is from an earlier version, you can upgrade your geodatabase and your network.
• The network dataset cannot have an unknown coordinate system.
• The network dataset cannot use any VB or Python script evaluators.
• The network dataset cannot use any custom COM evaluators.
• A network dataset that uses live traffic will be ported to a transportation network, but the live traffic components are excluded since they are not supported.

The following options are available:

• Include network data from the current map—Include all the network datasets referenced by the map.
• Do not include network data—Exclude network datasets from the Runtime content.

Locator

If your map contains a locator or composite locator, you can include the locator in your Runtime content. You can select one locator to add to the Runtime content. Create a composite locator if you want to include multiple locators. For more information, see Creating a composite address locator.

There are a few restrictions on which locators can be added to the Runtime content:

• The locator must be created with ArcGIS 10.0 or later.
• The locator cannot have an unknown coordinate system.
• The locator or any participating locator in a composite locator cannot be a geocoding service, including services from Portal for ArcGIS or ArcGIS Online.
• The locator cannot contain a custom plug-in in the locator style configuration.

The following options are available:

• Use a locator from the current map—Include the selected locator added to the map.
• Do not include a locator—Exclude any locators from the Runtime content.