Download an offline map (on-demand)
Your app can use a web map while it has no internet connection, by first downloading an offline map from the web map. As soon as the offline map is downloaded, a mobile worker can disconnect their device and work with the map offline.
Mobile users can specify a geographic area of a web map to download as an offline map. Offline maps defined and created this way are known as on-demand offline maps. On-demand offline maps are useful for mobile users who don't necessarily know in advance where they will be working.
The main advantage of on-demand offline maps is that your app can specify parameters to ensure that only essential web map content is included in the offline map, such as:
- The area of interest
- The max and min scales
- Which layers to include
- Which features to include
- Which related records to include
- Whether to include attachments
- Editing characteristics
The steps to use on-demand offline maps are:
- Create an offline map task
- Examine the web map's offline capabilities
- Create parameters to specify offline map content
- Create a job to generate and download an offline map
- Run the job
You should check which layers and tables in the web map can be taken offline by examining the web map's offline capabilities. This can help identify layers or tables that are missing in the offline map that is generated.
has property indicates that one or more layers or tables cannot be taken offline due to an error. You can check the
table to determine which layer or table cannot be taken offline, and why.
Some layers do not support being taken offline (either they have not been offline-enabled, or the type of layer does not support being taken offline). An offline map can still include references to these online-only layers, allowing the layers to be accessed and displayed whenever a network connection is available. This capability is set by
See Retain online services for more information.
When you generate and download an offline map, it should contain content relevant to the mobile user for the geographic area in which they will be working. Take care not to include more content than needed, because this can impact the time it takes to generate and download the offline map. Different parameters are available to control the geographic coverage area and the content of the generated offline map.
Get and examine the returned parameters. These default parameters represent the advanced offline settings configured by the web map author.
To override default parameters see Advanced parameters. For example, you can automatically update and display online-only layers when a network connection is available (see Retain online services). You can also set the max and min scale, use a local basemap, or set a definition expression on features.
To generate and download the offline map, you must create a
GenerateOfflineMapJob by providing the
GenerateOfflineMapParameters to the
generate method on
OfflineMapTask. You must provide a directory on the device to store the offline map. If this download directory already exists, it must be empty. If the directory doesn't exist, it will be created by the job.
If you want to control the individual layer and table content, you also need to provide the
GenerateOfflineMapParameterOverrides as well as the
generate result method on
OfflineMapTask. For more details see Create offline map parameter overrides.
See the Tasks and jobs topic for more details on how to work with jobs in general.
To generate the offline map and download it to your device, start the
GenerateOfflineMapJob. When complete, the job returns a .
If one or more tables or layers fails to be taken offline, the
has property may be true (however a layer may be configured for "online-only", which is not an error). You can check the
table dictionaries to identify problems.
Continue property of
false, the job terminates if any layer or table fails to be taken offline.
If you want to display the map immediately, pass the
Generate result to the map view.
Offline maps created by the on-demand workflow are stored in an unpacked mobile map package. When your app goes into the field, you need to open the map directly from this mobile map package
download stored on your device.
You can set properties on
GenerateOfflineMapParameters to control the offline map content. For example:
- The map's max and min scale
- Whether basemaps are included in the map
- Whether layers that reference online services are retained in the map
- Whether to allow synchronization of the map's geodatabases
- Whether to apply definition expression filters
- Whether to return all rows from a related table
- Whether to continue downloading the map if a single layer fails to be taken offline
- Including feature attachments
- Whether only the schema is provided for editable feature layers
- Update or replace the map's metadata
A web map might include image tiled layers, which are composed of many tiles at different levels of detail (similar to a “zoom level”). The amount of space, generation time, and download time required to download tiled layers in a web map will increase with every level of detail. To increase performance, you should only download the levels of detail that are relevant for your app. You can control this by setting the minimum and maximum scale parameters
If possible, choose a maximum scale that is not too “zoomed in” to prevent generating a large number of unnecessary tiles. Each service limits the number of tiles that can be taken offline. Make sure to set a scale range that avoids hitting this limit.
A web map author can define whether offline maps should:
Download the basemap defined by the web map. This is the default and ensures that a tile package is downloaded with the map.
Use a tile package that is already on the device. The tile package must be downloaded or copied onto the device separately and can be referenced with an absolute file path or a path relative to the map. Make sure the tile package covers the areas required by your map area. The benefits of this option are that the map file will be smaller, the download time may be faster, and you can use the tile package in many different maps and apps.
To use the tile package on your device, you must set the
referenceto the directory that contains the tile package. You should confirm that the tile package file,
reference, exists on the device before running the
GenerateOfflineMapJob. This job will add the tile package, as a basemap, to the offline map.
Avoid using the basemap. Developers can choose to override this configured behavior when they download an offline map from a web map. To do this, set the
s Include Basemap
false. In this case the
GenerateOfflineMapJobwill not download any layers included as part of the map's
Basemap. This task will not use the local tile package, even if you have specified one.
Live, online services are supported in offline maps. You can take a web map offline that has a mix of local on-device content as well as live, online service content (such as weather or traffic information). When network connectivity is available, users can use data from online services. Otherwise, only the local (offline) content is available.
A value of
Online means that any data that can't be taken offline will be accessed via the URL in the offline map. Your offline map retains all of the information from the original web map, but requires a network connection and may require authentication.
GenerateOfflineMapParameters is set to
sync. This mode allows you to synchronize any geodatabase changes with their online feature services.
If you want to avoid receiving any geodatabase updates, set the
update on the
n. This disables data synchronization on the map’s geodatabases and prevents the corresponding feature services from creating synchronization replicas. The benefits of this option are that the burden on the feature server is reduced and you will not need to unregister geodatabases when they are no longer required.
When taking a map offline, the
GenerateOfflineMapJob applies the feature layer's definition expression by default. Applying the definition expression may reduce the number of features taken offline for display and sync. If you do not want to apply the definition expression, set
If a map contains a layer or table with a relationship to another table, you can choose to download all rows or only related rows from the destination table. The default is to download only the related rows. If you want to return all rows, then you must set the value of
If the table is a standalone table or the source of a relationship, all rows are returned.
By default, the
GenerateOfflineMapJob continues to take layers and tables offline even if a layer or table fails. While this ensures that the map is taken offline, data may be missing. When the job completes, you should examine the job's result (discussed under Run the job) to identify if any layers have failed and determine whether or not to continue working with the map.
If you want the job to stop immediately when a layer or table fails, set the
Continue property to
false. This ensures that if a map is successfully taken offline it contains all of its layers and tables.
Failure to take a layer or table offline may be due to an intermittent network connection, loss of the service, or an unsupported layer type.
Some feature services contain attachments (pictures, videos, and other documents) for individual features. Because these files can be large, you should consider your app's offline workflow to determine whether the attachments need to be taken offline, and whether they need to be synchronized with the service when the app is connected. These two behaviors are defined using the
attachment properties on the
The return layer attachment property defines which layers should contain attachments in the offline map. The options are:
return- None of the layers contain attachments.
Layer Attachment Option.NONE
return- All layers have their attachments.
Layer Attachment Option.ALL_ LAYERS
return- Layers without editing enabled have attachments.
Layer Attachment Option.READ_ ONLY_ LAYERS
return- Layers with editing enabled have attachments.
Layer Attachment Option.EDITABLE_ LAYERS
The attachment sync direction defines how the attachments are synchronized with the service. The options are:
attachment- Attachments are not synchronized as part of the synchronization operation.
attachment- Attachments are uploaded from the client to the service, but any changes on the service are not downloaded to the client.
attachment- Attachments are uploaded from client to the service, and changes on the service are pulled down to the client.
Here are some workflows that describe how these two parameters affect each other:
Workflow 1 — Download attachments for all layers in the map, allow the user to add or remove attachments from the layers, and then synchronize these changes between the service and the client when online. For example: multiple users collect data on the same area and they want to synchronize all the changes with the centralized services as well as sharing changes with other people in the field.
Layer Attachment Option.ALL_ LAYERS
Workflow 2 — Download attachments for all read-only layers and update these layers when online. For example: users are offline and viewing a layer of buildings with photos that show how the buildings look. If there are any new photos added to the service, these will be downloaded to the client during synchronization when online.
Layer Attachment Option.READ_ ONLY_ LAYERS
Workflow 3 — Download attachments for editable layers only and upload them to the service when online. For example: users are offline and only need to view attachments for editable layers. If there are any read-only layers that provide context for the map, their attachments aren’t included to the local map. If users remove or add any new attachments, these changes can be synchronized to the service when online.
Layer Attachment Option.EDITABLE_ LAYERS
Workflow 4 — Do not download any attachments but allow any new attachments to be uploaded to the service when online. For example: users are offline and collecting new attachments in the field but do not need to view existing attachments.
Layer Attachment Option.NONE
If users are collecting new information in the field where they do not need to access previously created features, you can create an offline map with empty editable feature layers. Do this by setting the
Access an online map's metadata from the
item property. It includes portal item properties such as the title, description, short description, and thumbnail. This information is populated from the portal item that contains the map. You can override any of these metadata properties before you take the map offline. For example, if you are creating offline maps of different areas of interest on the same map, you may want to change the map's title to indicate which area it contains.
You can also create a new
OfflineMapItemInfo object and manually set all the details.
You may want to control how individual layers or tables are taken offline to do things like:
- Reduce the amount of data (for example, tile data) for a given layer
- Alter the spatial extent of a given layer (for example, to give coverage beyond the study area)
- Filter features (for example, with a where clause) to only take those that are relevant to your fieldwork
- Take features with null geometry (for example, where the attributes are populated in the office but the geometry needs to be captured on-site)
- Omit individual layers
- Define which layers should reference online content
GenerateOfflineMapParameterOverrides object provides control for these behaviors. It includes three dictionaries containing the generate geodatabase parameters (for feature layers), export vector tile parameters (for vector tile layers), and export tile cache parameters (for image tile layers), as well as two lists of layers and tables that will retain online access in the offline map (see Retain online services). Adjust any of these parameters and create the
GenerateOfflineMapJob using the overrides object.
To control how individual layers and tables are taken offline, follow these steps:
Generate the parameter overrides object (
GenerateOfflineMapParameterOverrides) using the
generatemethod on the
Offline M a p Parameter Overrides
OfflineMapTask. Provide the
GenerateOfflineMapParametersgenerated from the previous step.
When the task completes, a pre-populated
GenerateOfflineMapParameterOverridesobject will be provided. This is a modifiable layer-by-layer representation of the supplied
GenerateOfflineMapParametersand includes three dictonaries containing detailed parameters for each layer and table:
To override specific parameters for a layer, create a
OfflineMapParametersKey for the layer and use it to access the pre-populated parameters for that layer in the appropriate dictionary of the
GenerateOfflineMapParameterOverrides. You can then modify individual properties for taking that layer offline.
GenerateOfflineMapParameterOverrides also includes two lists which can be modified to specify which
ServiceFeatureTable objects should not have content downloaded but should instead access the original online data whenever a network connection is available (see Retain online services for more details).
Advanced symbols are supported only if they are defined in the original service. Any overrides with advanced symbols will result in empty symbols in an offline map.
Area-of-interest geometries that cross the dateline are not currently supported.
If more than one feature layer in a map refers to the same feature service endpoint, only one feature layer will be taken offline. The other feature layers will raise an error.