Download an offline map (preplanned)
Your ArcGIS Runtime 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.
The owner of a web map can define geographic areas of the web map to be packaged as offline maps before they are needed. Offline maps defined and created this way are known as preplanned offline maps. Preplanned offline maps are well-suited to field apps used by mobile workers and scale well to large workforces.
The main advantages of preplanned offline maps are:
- The map author can organize a set of specific map areas for mobile workers to use.
- Users can download the preplanned offline maps quickly and with minimal interaction. Since the preplanned offline maps are generated before they are needed, their download time is comparable to any other files and resources.
- Many users can download the same preplanned offline map.
The steps to use preplanned offline maps are:
- Create preplanned offline maps for your web map.
- Get a list of map areas in your app.
- Create the parameters
- Create the job
- Run the job
To create preplanned offline maps, you must use web maps created with ArcGIS or with ArcGIS Enterprise 10.6.1 or later. You must ensure that all services used in the web map are enabled for offline use.
You can create map areas manually using the ArcGIS Online or ArcGIS Enterprise. You can also create them programmatically, using Python scripts or the ArcGIS REST API, as described below.
Use ArcGIS Online or ArcGIS Enterprise to create, edit, and manage map areas for your web maps. See the topics below for details.
- Update the map area of an offline map and any of its packages that have been deleted or contain more recent data.
- Delete an individual data package.
- Delete an offline map along with its associated packages.
- Inspect any of the offline maps's packages.
- List the web map's current map areas.
Use the ArcGIS REST API if you need even more control when creating your preplanned offline maps. There are two stages to this process:
- Create an offline map: Run the Create Map Area task with a bookmark or geographical extent to define the area of interest for a web map that's enabled for offline use. The task generates a new portal item of type
MapArea. Only the owner of the web map and organization administrators can run this task.
- Create the data defined by the map area: Run the Setup Map Area task with the map area portal item ID. This creates a set of data files such as tile packages, vector tile packages, and SQLite geodatabases. For good data management, you should organize these files into folders. Only the owner of the map area portal item owner and organization administrators can run this task.
In addition to creating the map area, you can also define how users receive updates to the data used in the offline map. Updates can come from the synchronization of the offline map's geodatabases with their online services or by applying scheduled update files to the geodatabases.
- Synchronization allows you to download updates from the online service and upload edits from the offline map when connectivity is available. You can configure the synchronization direction control how edits are synchronized —download only, upload only, or bi-directional.
- Scheduled updates provide feature service updates in a file that is created on a regular basis. ArcGIS Runtime API can download the required files and apply their updates to the offline map's geodatabases. These files are relatively small so they are quick to download and fast to apply. This provides a scalable solution for receiving updates to read-only geodatabases and is useful when you need to provide many clients with an up-to-date read-only copy of the feature data. If your geodatabase supports creating new features, then clients may also upload new features to the map as part of the scheduled updates workflow. You can set the scheduled update parameters using the Setup Map Area task in the ArcGIS REST API.
Once you have created a preplanned map area, the mobile map package publication will be initiated. The following section describes how you build a Runtime app to download the mobile map package for offline map.
Each web map can have up to sixteen preplanned offline map areas defined, which are available to download as offline maps. Your app needs to determine which map area to download. You can do this by allowing the mobile worker to select a map area from a map view or from a list of map areas. Alternatively, the app logic could select a map area for the mobile worker.
Follow these steps to retrieve all of the map areas:
- Instantiate the offline map task by passing either a map (created from a web map) or a web map's portal item to the
- Retrieve a list of the preplanned map areas from the web map using the
preplannedMapAreas()method on the
- Load the preplanned map area;
- Display the map area titles and thumbnails in a list, or show the map area extents or just select a map area by name.
To download a preplanned offline map to your device, you should provide a set of
DownloadPreplannedOfflineMapParameters. To obtain a set of default parameters pass in the map area to
OfflineMapTask::createDefaultDownloadPreplannedOfflineMapParameters(). The value of these default parameters will match the advanced offline settings configured by the web map author (discussed in Take web maps offline).
To ensure the job was successful, check the following:
- If at least one table or layer failed to be downloaded successfully,
true. In that case, you should examine the layerErrors() and tableErrors() dictionaries in that result object to identify the problem.
- The job's
parameters()method returns a reference to the
DownloadPreplannedOfflineMapParameterswith which the job was created. If
isContinueOnErrors()in that parameters object is
false, then the job will be terminated immediately if a single layer or table fails to be taken offline.
- If the preplanned offline map publishing has failed, or is still in progress, you will not be able to download its mobile map package. Before running this job, you can check whether the publishing process is complete, has failed, or is still in progress by examining the
PreplannedMapArea. (Note: The download preplanned offline map job has a a
parameters()function that returns the job's
DownloadPreplannedOfflineMapParameters, which contain
If you want to display the map immediately, then use
Offline maps created by the preplanned workflow are stored in an unpacked mobile map package. When your app goes into the field, you will need to open the map directly from the mobile map package's download directory stored on your device.
Once you have the default parameters you can customize them in the following ways:
DownloadPreplannedOfflineMapJob downloads a map's tables and layers for offline use. By default this job will continue doing so, even if one table or layer has failed. Failures could be due to an intermittent network connection, loss of the service, or an unsupported layer type. The approach ensures that you can take a map offline but you may have some data missing.
To ensure that the offline map contains all of its layers and tables, you can request that the job be stopped if any layer or table fails to download. To do this,
The author of the web map can define whether the map uses:
The basemap defined by the web map.
This is the default situation and ensures that a tile package is downloaded as part of the mobile map package.
A tile package that is already on the device.
The tile package must be downloaded or copied onto the device and can be located using an actual file path on the device or a path that is relative to the mobile map package. You must ensure that the tile package covers the areas required by your offline map(s). The benefits of this option are that the mobile map package 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, employ certain functions in
setReferenceBasemapDirectory()and pass in the directory which contains the tile package.
- Confirm that the tile package file,
referenceBasemapFilename(), exists on the device.
Only then should you run the
DownloadPreplannedOfflineMapJob. This job will add the tile package, as a basemap, to the offline map.
If you only want to take the operational layers offline, you can programmatically exclude the basemap by setting
false. In that case, the
DownloadPreplannedOfflineMapJobwill not download layers included as part of the map's basemap. (For more information, see
Mapor its base class
GeoModel.) This task will not use the local tile package, even if you have specified one.
Your local geodatabase can receive updates from its online feature services. The
DownloadPreplannedOfflineMapParameters::updateMode() parameter indicates how this operates via one of four possible
PreplannedUpdateMode enum values.
Synchronize with the feature services.
This flexible option allows you to edit the local geodatabase and synchronize it with its online feature services. This enum value is
Download scheduled updates.
The web map author can specify that scheduled updates are generated for the feature services in the map (discussed in Define updates). This option means that the local geodatabase can only receive updates via the scheduled update files. You cannot create, update, or delete features in the local geodatabase. This enum value is
Download scheduled updates and upload new features.
The web map author can specify that scheduled updates are generated and that the map supports the creation of new features. This option means that, while the local geodatabase can receive updates from its feature services via the scheduled update files, you can also create new features that can be uploaded to the feature services. This enum value is
No updates from the feature services.
If you want to avoid receiving any updates to the local geodatabase, use the enum value
PreplannedUpdateMode::NoUpdates. This option disables data synchronization with the map’s geodatabases and prevents the corresponding feature services from creating synchronization replicas. The benefits are that the burden on the feature server is reduced and you will not need to unregister geodatabases when they are no longer required.
Once you have obtained the offline map follow these steps:
- Display and interact with the maps, layers and data offline. Explore and edit the feature data, if necessary.
- Update an offline map by synchronizing your edits with the online services, when connectivity is restored.
- Finish using an offline map by unregistering any geodatabases and fully releasing all locks on the mobile map package.