Prepare maps

While Navigator can be used to create routes directly in the app using Esri-provided navigation maps, you can also create custom navigation maps that allow you to navigate on your own roads and to your own assets.

Using ArcGIS Pro, you can customize the Esri-provided navigation maps or create your own navigation map with your organization's basemaps, road networks, assets, asset locators, and travel modes, and share this with your mobile workers to use when getting directions in Navigator.

A navigation map is a mobile map package (MMPK) that includes the following components:

  • Transportation network—A road network that supports routing and a geocoding locator.
  • Basemap—The background data displayed under your route and operational layers. Basemaps can be compressed to improve performance on mobile devices.
  • Locator (optional)—Allows mobile workers to search for locations or assets. Locators can be created based on operational layers or by creating an address locator.
  • Operational layers (optional)—Contain your organization's assets. For example, a utility company's assets could include power line supports.
  • Custom travel mode (optional)—Enables workers to calculate a route based on how they travel to a destination. For example, you can create a travel mode for a truck that accounts for height or U-turn restrictions.

Once you have all the components you need for your navigation map, consolidate them in a mobile map package in ArcGIS Pro. This file can be shared with your ArcGIS organizational account so mobile workers can download and use it in Navigator. For more information, see the mobile map package introduction in the ArcGIS Pro help.


If an exercise that walks you through each step for creating an MMPK would be helpful, see the Exercises section for complete examples.


The following products and licenses are required to create custom navigation maps for use with ArcGIS Navigator:

  • ArcGIS Pro 1.2 or later (recommended, and referenced in this topic: ArcGIS Pro 2.3).
    • Creating custom navigation maps with your organization's assets, locators, and roads requires ArcGIS Pro 1.2 or later.
    • Creating travel modes and using feature editing templates requires ArcGIS Pro 1.4 or later.
    • Sharing MMPKs through the Share tab (where packaging and sharing is accomplished in a single step) requires ArcGIS Pro 2.2 or later. In earlier versions of ArcGIS Pro, MMPKs can be created and shared with the Create Mobile Map Package and Share Package tools.
  • An ArcGIS organizational account with licensing for the following:
  • (Optional) A license to use the ArcGIS StreetMap Premium dataset—Required to include the StreetMap Premium roads in your MMPK.
  • (Optional) A license to use the StreetMap Premium Custom Roads dataset—Required to include the StreetMap Premium roads and your own roads in your MMPK.
  • (Optional and recommended) A mobile device with ArcGIS Navigator installed—For testing your MMPK.

Your ArcGIS organizational administrator configures the licenses for your ArcGIS organizational account.


If you don't have an ArcGIS organizational account, sign up for a free trial.

If you are a member of an organization on ArcGIS Online and need an ArcGIS Navigator trial license added to it, request a free trial.

Set up a project in ArcGIS Pro

To create a mobile map package, you need to create a project in ArcGIS Pro. Once created, how you bring data into your project depends on what you want to do.

Connect your roads to StreetMap Premium (optional)

If you need to route on roads that aren't included in StreetMap Premium (for example, your organization's private roads) and you don't have your own transportation network, use the StreetMap Premium Custom Roads dataset. You'll create or load your roads into your copy of the StreetMap Premium network dataset. Once you've created or loaded your roads, you will need to build and test your new road network.


When creating or loading roads into StreetMap Premium Custom Roads for use in Navigator, the workflow outlined below must be followed. For complete steps, see the exercises on creating roads or loading roads. For additional documentation, see StreetMap Premium Custom Roads.


Creating or loading roads requires the StreetMap Premium Custom Roads license and data.

Create roads

If your roads don't already exist as a file geodatabase feature class, digitize them and attach them to the StreetMap Premium Custom Roads dataset as follows:

  • Open the project file that comes with StreetMap Premium Custom Roads in ArcGIS Pro. Detailed instructions are available in the Readme.txt file packaged with the data.
  • If you have operational layers that you would like to use for reference when digitizing, add them to the Add Custom Streets map tab of your project.

    If you would like the layer to appear on the map in Navigator, you'll also need to add it to the Navigation with Custom Streets map tab. See Add and customize layers.

  • To accurately place your roads when digitizing, zoom in on the map to the area where you need to digitize them.

    Create bookmarks of the areas you're working in at the zoom level you use most to make it easy to return to them.

  • Enable snapping and ensure that point, end, vertex, and edge are enabled.
  • Use the Custom Streets feature editing templates to make it easier to connect streets—The templates automatically create the feature geometry needed to connect streets based on the network dataset rules. Specify the street name and whether the road you are adding is paved.

    In the feature attribute table, you can add additional optional attributes that determine how a route is calculated. For details on the attributes you can populate, see Network attributes. To make edits in the feature attribute table, see Enter attributes for new features.

  • Digitize your roads. Start each road by clicking the point where the road you are digitizing intersects with a road in the Routing Streets layer. End each road by right-clicking the last vertex, clicking Finish, and clearing the selection.

    For more information about connecting road networks, see Understand connectivity and the documentation provided with your copy of StreetMap Premium Custom Roads.

For complete steps, see Add assets and digitize roads.

Load roads

If you already have roads in a file geodatabase feature class, you can attach them to the StreetMap Premium Custom Roads dataset as follows:

  • Open the project file that comes with StreetMap Premium Custom Roads in ArcGIS Pro. Detailed instructions are available in the Readme.txt file packaged with the data.
  • If you have operational layers that you would like to use for reference, add them to the Add Custom Streets map tab of your project.

    If you would like the layer to appear on the map in Navigator, you'll also need to add it to the Navigation with Custom Streets map tab. See Add and customize layers.

  • Load your road data into the Custom Streets feature class with the Append tool.

    If your road network schema does not match the StreetMap Premium Custom Roads schema, set the Schema Type to Use the Field Map to reconcile schema differences.

For complete steps, see Add assets and load roads.

Build and test the new road network

The custom streets you just created or loaded aren't yet part of your copy of the StreetMap Premium Custom Roads network dataset. They won't be used in routes until you rebuild the Routing_ND network dataset. Once it's rebuilt, test your new network to identify and address any road connectivity or routing problems.

  • Use the Build Network tool to rebuild the Routing_ND network dataset.
  • Test your new road network—Add stops to a route that includes StreetMap Premium roads and the roads you created or loaded, then generate directions.

    Always save pending edits before running the Build Network tool.

    If a route was not generated, try building the road network again.

When connecting roads to the StreetMap Premium Custom Roads dataset, you may encounter the problems listed below. See the Examine and fix road data problems example for detailed steps that show how to resolve these issues:

  • Unconnected roads—Roads that intersect but are not connected.
  • Unconnected crossing roads—Roads that cross but have not been connected.
  • Disconnected custom roads—Custom roads must be connected with a custom streets override point.
  • Disconnected StreetMap Premium roads that intersect with custom roads—Custom roads must be connected to StreetMap Premium roads with a custom streets override point.
  • Duplicate roads—If a road is already included in the Routing Streets feature class, it should be removed from the custom streets feature class.

Remove the route layer you created to test your road network before packaging the MMPK.

Add and customize layers

Your mobile workers might want to see your assets in the MMPK. Add operational layers that contain your assets to help mobile workers view, search for, and route to your assets. Once added, customize the layer for your mobile workers. For example, you can do the following:

  • Customize the symbology and layers—Make it easier for mobile workers to see and locate your assets, ensuring that they route to the correct assets. For example, you can do the following:
    • Choose a simple, familiar symbol.
    • Make the symbol size easy to see on a mobile device (10 pt is a good size for most mobile devices).
    • Make labels easy to read over the basemap (a label size of 11 and a 1 pt white halo are helpful).
    For complete steps, see Customize the map symbology and labels.
  • Configure pop-ups—When an asset is tapped in Navigator, display the information your mobile workers need. See Customize pop-ups for details.

    If features don't have pop-ups, users can't interact with them on the map.


The map's coordinate system is determined by the coordinate system of the first layer you add. To choose a coordinate system that is appropriate for your map, set it in the map's options.

Enable search

Your mobile workers might need to search for an asset, address, or intersection to route to the correct one, or to find information to help them in their work. The search available in Navigator is defined in the MMPK and can be customized as follows:

  • Enable searching for assets—If you included assets in your MMPK, make them searchable by specific fields so mobile workers can more easily locate them. There are two ways to make your assets searchable: For complete steps, see Enable searching for assets.
  • Enable searching for street addresses or intersections by including a locator in your ArcGIS Pro project.

    This might be a general address locator that was included with the Esri-provided navigation maps or the StreetMap Premium dataset, or you might have created your own address locator.

  • Verify your layer or locator is correctly included in your project.
    • For a layer, it must appear in the project's list of locate providers. This is also where you'll enable and configure it.
    • For general or custom address locators, they must appear in the project's Locators folder. Your can configure their order in the list of locate providers.
  • Order the list of locate providers to reflect the order in which search results should display.
  • Test your search, making sure the expected assets, addresses, and intersections are returned. The map should zoom to selected search results and show their details.

Add a custom travel mode

Travel modes provide restrictions on the travel and the routes that can be created. Travel modes are associated with a specific MMPK and can be selected by drivers in Navigator. StreetMap Premium and the Esri-provided navigation maps include default travel modes. You can also add a custom travel mode to suit the needs of your drivers and their vehicles. You'll provide a description and select the appropriate type of transportation. Configure the costs, restrictions, U-turn settings, and any additional advanced settings based on your needs and your network dataset's attributes. For complete steps, see Create your own travel mode.


If you want drivers to use your travel mode by default for your MMPK in Navigator, set your custom travel mode as the default travel mode in the travel mode settings.

If you are using a StreetMap Premium dataset, change the Distance Cost units from miles to kilometers. All of the StreetMap Premium parameters are in terms of the metric system, and the distance cost units must match.

Once your travel mode is created, test it in ArcGIS Pro. Create a route layer, add stops to the route that test the restrictions you selected when setting up your travel mode, and make sure your new travel mode is selected on the Route tab. For example, place stops on either side of a bridge that is lower than the vehicle height restriction specified in your custom travel mode. Run the route analysis. Compare the results of your custom travel mode with the results of one of the default travel modes to make sure the desired routing behavior occurs. For complete steps, see Test your travel mode.


Delete any route layers you created after testing to prevent accidentally packaging them in the MMPK.

Package and share the MMPK

Combine all of the navigation map components in your ArcGIS Pro project into a mobile map package and share it with your mobile workers. See Share a mobile map package, keeping in mind the following considerations:

  • Save the package to your account to make it available to mobile workers using Navigator.
  • Zoom to the desired map extent and include the data of the current display extent in the package. Clip to make sure features partially outside the extent (such as long roads) only have the sections in the map extent included in the package.
  • Indicate whether you want to include an address locator and, if so, select it from the menu or browse to its location.
  • Specify the location to store the MMPK in your portal content and share with your organization or specific groups.
  • Specify with whom the MMPK should be shared.

    If you share the package with specific groups in your organization, make sure that your mobile workers belong to those groups.

  • Analyze the MMPK to discover and resolve package problems.

It may take some time for the Package Mobile Map tool to run.

Once your package is created and shared, mobile workers can sign in to Navigator, search for the package, download it to their device, and start navigating.


If you need to make multiple similar mobile map packages, automate the process with Python using the Create Mobile Map Package and Share Package tools.

For complete steps, see Package and share the data.

Test the map in Navigator

Before distributing your MMPK for use in the field, download and open it in Navigator and make sure it functions as expected. Make sure to test it outside, and not just in your office, because what works on a mobile device screen is influenced by glare and lighting. Pay attention to the following:

  • Routing is successful and returns the expected routes, including routing on your roads if any were included.
  • Your assets appear as expected, with clear, easy-to-see, and informative symbology and labels.
  • Searching for assets, street addresses, and intersections returns the expected results.
  • The correct default travel mode is used for routes.
  • Routing with your custom travel mode generates routes that honor the restrictions of your custom travel mode.

For complete steps, see Test the map in Navigator.


Navigation maps for Navigator have the following limitations:

  • Basemaps composed of map services or raster files aren't supported. This includes basemaps provided by Esri through ArcGIS Online.