Once your map is ready for use in the field, deploy it to your mobile workers. Share it with them, then they can either browse to the map in ArcGIS Field Maps or tap a custom link you've sent. When mobile workers need to work offline, they can download maps you've prepared, or they can copy MMPKs directly to their device. Provide your mobile workers with help on using the app by customizing a field guide for your organization's data collection projects. You can also use mobile device management (MDM) software to deploy and configure the mobile app.
Share your map for use in Field Maps
Field Maps provides access to maps that are either owned by a mobile worker or shared with an ArcGIS organization or group containing the mobile worker. Creating a group is optional, but it can help you manage the mobile workers who have access to your maps and data. For your mobile workers to access your shared map, they need to be members of an ArcGIS organization. If your shared map is enabled for editing, they will also need to have the privilege to edit features.
- If the mobile workers aren't already members of an ArcGIS organization (either in ArcGIS Online or ArcGIS Enterprise), create accounts for them.
See Invite and add members in ArcGIS Online or Add members to your portal in ArcGIS Enterprise.
The accounts you create must meet the ArcGIS account requirements for using Field Maps.
- Share the map and layers with the ArcGIS organization or create a group to manage access to your maps and data.
- Share the map and layers with the ArcGIS organization—You can configure sharing in the Field Maps web app, or you can Share items with your organization in ArcGIS Online or Share items with your organization in ArcGIS Enterprise.
- To create a group to manage the mobile workers who have access to your maps and data, do the following:
- Create a group—See Create groups in ArcGIS Online or Create groups in ArcGIS Enterprise.
- Add the mobile workers to the group—See Configure groups in ArcGIS Online, Manage groups for a specific member in ArcGIS Online, or Manage groups for a specific member in ArcGIS Enterprise. If you are using ArcGIS Enterprise and have an enterprise identity provider (IDP), you can link enterprise groups to your portal group.
- Share the map and layers with the group—You can configure sharing in the Field Maps web app, or you can Share items with a group in ArcGIS Online or Share items with a group in ArcGIS Enterprise.
Open your map from a link
Mobile workers can browse to your map in Field Maps, or you can provide a URL directly to it. Make it easy for your mobile workers to open the right map and get started on their work by sharing a link directly to your map through an email, text message, web page, or another app. Use links to Field Maps that, when tapped, open Field Maps to the map you want mobile workers to use. If the map is enabled for editing, they can start capturing data when the map opens. If your mobile workers are working offline, the links still work.
Field Maps links
Field Maps links have the following format: https://fieldmaps.arcgis.app?parameter=value¶meter=value, where parameter and value pairs are replaced with the values you want to use to open a map. For example, https://fieldmaps.arcgis.app?referenceContext=center&itemID=3ac4145c1ac44aea86e9ed42e00fbb0d¢er=34.0547155,-117.1961714 uses the parameter itemID and the value 3ac4145c1ac44aea86e9ed42e00fbb0d to open the map with that ID. The referenceContext parameter and its value center specify the type of action that should be performed in the app—in this case, centering the map. The center parameter and 34.0547155,-117.1961714 value provide the coordinates at which to center the map.
Parameters
The following parameters are supported with Field Maps links. If no parameters are passed, tapping the link opens Field Maps (or prompts you to open the app).
| Parameter | Values | Notes |
|---|---|---|
anonymousAccess | Used when calling a map or MMPK that is shared publicly and will not require signing in to access |
|
bookmark | Specifies a bookmark from the map |
|
callback | The URL to call when capturing the asset or observation is complete |
|
callbackPrompt | Prompts the mobile worker before executing the callback and displays this value in the prompt as where the mobile worker will be taken |
|
center | A set of latitude, longitude (y, x) coordinates at which to center the map |
|
featureAttributes | A JSON dictionary of form entries for the newly captured feature |
|
featureID | Uniquely identifies the feature within the layer to be updated. Must be a GlobalID field. |
|
featureSourceURL | The URL of the layer where capture is instantiated |
|
geometry | Defines the location for the newly captured feature |
|
itemID | The itemID of the map to open |
|
portalURL | Your organization's portal URL |
|
referenceContext | What the app should do, if anything, once open and the user is signed in | The following values are supported:
Note:If you want to use multiple ReferenceContext values in a single URL, such as open and search, only specify one value—the primary use of the ReferenceContext parameter. For example, specifying search implies that the map is open. See the Field Maps link examples below. |
scale | The scale (in map units) at which the map should be rendered |
|
search | An address, place, coordinate, or feature to search for |
|
trackingDuration | Specify the duration of tracking in hours. |
|
trackingON | Specify whether location tracking is turned on or off. |
|
useAntennaHeight | Specifies whether the antenna height of the current receiver is subtracted from the z-value of each vertex of the location |
Note:Support is coming to Android. |
useLocationProfile | Specifies whether the current location profile is used to transform the location |
Note:Support is coming to Android. |
wkid | Specifies center coordinates in a different spatial reference |
|
Continue reading for examples of using these parameters to achieve specific behavior with a Field Maps link.
Open the map
Use the following parameters to open the map:
- referenceContext=open
- itemID
- portalURL (optional)
Supported map types include web maps, MMPKs, and offline areas.
The following are examples:
- Open the map as the currently signed-in mobile worker, or if not signed in, provide the opportunity for them to sign in: https://fieldmaps.arcgis.app/?referenceContext=open&itemID=0c900ae2a1084d27b608233921ef1a84
- Connect to a specific portal and open the map: https://fieldmaps.arcgis.app?referenceContext=open&portalURL=https://myportal.mycompany.com/arcgis&itemID=0c900ae2a1084d27b608233921ef1a84
Access a public map without signing in
Use the following parameters to access a public map:
- referenceContext=open
- itemID
- anonymousAccess=true
- portalURL (optional)
The following is an example:
- https://fieldmaps.arcgis.app/?referenceContext=open&itemID=5dce807aeb5c4b33bce767d278df9c3d&anonymousAccess=true
Center and scale the map
Use the following parameters to specify the center and scale of the specified map instead of using the default map center and scale settings when the map is opened:
- referenceContext=center
- itemID
- center
- scale (optional)
- wkid (optional)
- bookmark (optional)
The default coordinate system is WGS84, but this can be changed by using the wkid parameter.
The following are examples:
- Center on a latitude/longitude coordinate pair (WGS84) with the scale set to 3000 map units: https://fieldmaps.arcgis.app/?referenceContext=center&itemID=0c900ae2a1084d27b608233921ef1a84¢er=41.780618,-88.179449&scale=3000
- Center on coordinates in the NAD83/UTM Zone 19N (WKID: 26919) spatial reference system with the scale set to 1000 map units: https://fieldmaps.arcgis.app/?referenceContext=center&itemID=0c900ae2a1084d27b608233921ef1a84¢er=4807094.81,-1096767.71&scale=1000&wkid=26919
Search in a map
Use the following parameters to open the map and search for an address, place, coordinate, or feature (asset or observation):
- referenceContext=search
- itemID
- search
The following are examples:
- Search for an address: https://fieldmaps.arcgis.app/?referenceContext=search&itemID=15c3a41bc01e4f8b9922736f3c194c29&search=899+Aurora+Ave,+Naperville,+Illinois
- Search for a place from the geocoder: https://fieldmaps.arcgis.app/?referenceContext=search&itemID=15c3a41bc01e4f8b9922736f3c194c29&search=Gas+Station
- Search for coordinates: https://fieldmaps.arcgis.app?referenceContext=search&itemID=bd171bc8ba404b14a2e845fe6839e881&search=34.0547155,-117.1961714
- Search for an asset in the map, for example, Hydrant #43141: https://fieldmaps.arcgis.app/?referenceContext=search&itemID=0c900ae2a1084d27b608233921ef1a84&search=43141
View a bookmark
Use the following parameters to view the location specified by a bookmark from the map:
- referenceContext=center
- itemID
- bookmark
The following example link opens the map to a bookmark named Centennial Park:
Initiate capturing a feature
Open the map and start capturing a feature using the following parameters. Optionally, provide form entries to apply to the new asset or observation.
- itemID
- referenceContext=addFeature
- featureSourceURL
- geometry (optional)—If provided, defines the shape of the feature. If not provided, the mobile worker's GPS location is used for the point or the first vertex if a line or polygon.
- useAntennaHeight (optional)
- useLocationProfile (optional)
- featureAttributes (optional)
- callback (optional)
- callbackPrompt (optional)
Note:
Support for useAntennaHeight, useLocationProfile in links is coming to Android.
The following are examples:
- Initiate capture at the mobile worker's location without providing any form entries:
- Initiate capture at a specific location and provide form entries to apply to the new asset or observation:
Note:
Form entries you pass into the new asset or observation need to be URL encoded. The unencoded URL is provided below to make it easier to read the example and understand the entries provided.
- Without URL encoding—https://fieldmaps.arcgis.app?referenceContext=addFeature&itemID=3ac4145c1ac44aea86e9ed42e00fbb0d&geometry=34.0547155,-117.1961714,1200&featureSourceURL=https://services9.arcgis.com/QjGvjfQhsHAmqfjP/arcgis/rest/services/DamageAssessment_Apr2018_631d0895e7d3404bb78e8e04e92d896e/FeatureServer/1&featureAttributes={"incidentid":"527","inspector":"Frank Jones","inspdate":1502917218285}
- With URL encoding of form entries—https://fieldmaps.arcgis.app?referenceContext=addFeature&itemID=3ac4145c1ac44aea86e9ed42e00fbb0d&geometry=34.0547155,-117.1961714,1200&featureSourceURL=https://services9.arcgis.com/QjGvjfQhsHAmqfjP/arcgis/rest/services/DamageAssessment_Apr2018_631d0895e7d3404bb78e8e04e92d896e/FeatureServer/1&featureAttributes=%7B%22incidentid%22:%22527%22,%22inspector%22:%22Frank%20Jones%22,%22inspdate%22:1502917218285%7D
- Initiate capture with a provided polygon geometry (in WGS84) without providing any form entries:
- Initiate capture at a specific location without providing any form entries, but use the antenna height to calculate the z-value and use the current location profile to transform the point as if it is from the GPS:
- Initiate capture and automatically open another app (in this example, ArcGIS Navigator) when capture completes:
- Initiate capture and open another app after prompting (in this example, ArcGIS Navigator) when capture completes:
Initiate updating a feature
Open the map and start updating an existing feature using the following parameters. Optionally, provide form entries to apply to the updated asset or observation.
- itemID
- referenceContext=updateFeature
- featureSourceURL
- featureID
- featureAttributes (optional)
- callback (optional)
- callbackPrompt (optional)
Note:
This does not apply to table rows.
The following are examples:
- Initiate updating a feature without providing any form entries:
- Initiate updating a feature and provide form entries to apply to the updated asset or observation:
Note:
Form entries you pass into the updated asset or observation need to be URL encoded. The unencoded URL is provided below to make it easier to read the example and understand the entries provided.
- Without URL encoding—https://fieldmaps.arcgis.app?referenceContext=updateFeature&itemID=3ac4145c1ac44aea86e9ed42e00fbb0d&featureSourceURL=https://services9.arcgis.com/QjGvjfQhsHAmqfjP/arcgis/rest/services/DamageAssessment_Apr2018_631d0895e7d3404bb78e8e04e92d896e/FeatureServer/1&featureID=bb0a0c92-9f53-4367-a6a1-bc6edc605be0&featureAttributes={"incidentid":"527","inspector":"Frank Jones","inspdate":1502917218285}
- With URL encoding of form entries—https://fieldmaps.arcgis.app?referenceContext=updateFeature&itemID=3ac4145c1ac44aea86e9ed42e00fbb0d&featureSourceURL=https://services9.arcgis.com/QjGvjfQhsHAmqfjP/arcgis/rest/services/DamageAssessment_Apr2018_631d0895e7d3404bb78e8e04e92d896e/FeatureServer/1&featureID=bb0a0c92-9f53-4367-a6a1-bc6edc605be0&featureAttributes=%7B%22incidentid%22:%22527%22,%22inspector%22:%22Frank%20Jones%22,%22inspdate%22:1502917218285%7D
Initiate location tracking
Use the following parameters to enable location tracking and set a tracking duration:
- referenceContext=track
- trackingON=true
- trackingDuration
The following example link turns location tracking on for 120 hours:
https://fieldmaps.arcgis.app/?referenceContext=track&trackingOn=true&trackingDuration=120
Note:
You can also use a link to turn location tracking off. For example:
https://fieldmaps.arcgis.app/?referenceContext=track&trackingOn=false
Provide help to your mobile workers
While this documentation provides information about using Field Maps, mobile workers collecting data in the field often need something more lightweight—something that can be printed and taken along (especially if working offline). Providing them with a basic, single-page field guide that helps with common tasks and some issues makes your job supporting the mobile workers easier. A field guide template focused on common data collection tasks and written for the mobile worker is provided. Use it to start creating your own reference for your mobile workers.
- Download the field guide template.
- Customize it (add your logo, troubleshooting tips specific to your organization, and so on). Be sure to remove the first section that includes the customization steps.
- Give it to your mobile workers.
Mobile workers can keep the guide in their pocket and use it to resolve issues while they're in the field.
Mobile device management
Mobile device management (MDM) refers to software used for the administration of mobile devices in an organization. An MDM is used to enhance data and network security as well as to set and enforce mobile device policies. Additionally, using an MDM increases the efficiency of app deployments and management for mobile devices, including controlling how and when an app is updated. To learn more about how Esri approaches MDM, see ArcGIS Secure Mobile Implementation Patterns in the ArcGIS Trust Center.
When preparing to deploy Field Maps to your organization's mobile devices via MDM, there are some application and profile settings you may want to configure. These include the portal URL and per-app VPN settings.
Field Maps app configuration
App configuration (also referred to as AppConfig) refers to a format for providing application settings such as portal URL, among others. Instead of configuring these settings manually each time a mobile app is installed, you can use your MDM to specify and apply app configurations automatically. These settings are defined as a dictionary of key-value pairs in an XML file. How the dictionary is created depends on the MDM you're using. To learn more about app configuration, visit the AppConfig Community.
Field Maps has the following settings that can be implemented with app configuration in your MDM:
| Key | Value | Notes |
|---|---|---|
anonymousAccess | Specifies whether to sign in anonymously or require credentials |
Note:When connected to a portal anonymously, public maps in Featured Groups appear in the Maps list. Mobile workers can search for any publicly shared map in the portal. |
portalURL | Your organization's portal URL |
|
trackingUploadLKLFrequency | Specifies the last known location upload frequency |
|
trackingUploadTracksFrequency | Specifies the track upload frequency |
|
useInAppAuth | Specifies whether a webview is used for sign in and authentication in Field Maps |
Caution:If a VPN is required to access your internal resources, and your organization restricts VPN access to browsers on managed devices, setting useInAppAuth to true may be required for enabling successful sign in to your portals. |
Note:
If Field Maps is opened with a Field Maps link, the link parameter values take precedence over app configuration settings.
Per-app virtual private network
Configuring a per-app virtual private network (per-app VPN) in your MDM allows you to restrict access to internal resources to specific managed apps. Field Maps can be deployed with this configuration. To set up per-app VPN for use with Field Maps, see the software documentation for the MDM you are using.
Caution:
If you're on iOS and using ArcGIS Online or ArcGIS Enterprise 10.6.1 or later, Safari is used to display the portal sign-in screen in Field Maps. For this to work correctly with a per-app VPN enabled, your portal domain (for example, mycompany.com) must be specified in the Safari Domains setting in the per-app VPN profile you're using. If Safari Domains is not set correctly, the assigned mobile devices cannot access the Field Maps portal sign-in screen. The alternative to this is to set useInAppAuth to true, which will force the sign in process to happen in an in-app webview, as opposed to in Safari.
When you set a Safari Domain in the per-app VPN profile as described above, the Safari Browser app can also access the portal domain you specified in the Safari Domains setting. If you want to block this access, configure an iOS Restriction (if available in your MDM) to Block Safari Browser App on the desired devices.
If you're on Android and using ArcGIS Online or ArcGIS Enterprise 10.6.1 or later, Chrome Custom tabs (or your preferred browser) is used to display the portal sign-in screen in Field Maps. The browser must have VPN access for this to work correctly with a per-app VPN enabled. Consider setting useInAppAuth to true to avoid this requirement and force the sign in process to happen in an in-app webview.
After you've configured the per-app VPN settings for Field Maps in your MDM, when the app is opened on a managed mobile device, it automatically connects to the designated per-app VPN. When Field Maps is running in the background, the per-app VPN is still connected, but only to Field Maps. When Field Maps is closed, the mobile device automatically disconnects from the per-app VPN.