MobileMap 5.0 represents a significant evolution for the MobileMap application. Many of the changes that have been made, however, are changes to the underlying technology rather than changes that affect user interfaces or workflows. The biggest changes are that MobileMap 5.0 leverages updated versions of the ArcGIS and Android Software Development Kits (SDKs). These help to ensure that MobileMap complies with enhanced Android security measures and updated Android and ArcGIS capabilities.
The most notable change to MobileMap is the adoption of the ArcGIS sync framework. When MobileMap was first released in 2013, ArcGIS did not support offline data access or sync. To support this critical functionality, WSG build our own sync framework. Over the years, we have updated our sync framework while tracking the encouraging advancements in ArcGIS capabilities. MobileMap 5.0 is our first release to utilize ArcGIS sync framework and we are excited about the improvements that this update brings to MobileMap workflows. This change also means that the underlying offline database has changed from a custom SQLite database to an ArcGIS Offline Geodatabase.
In addition to this ArcGIS SDK update, the Android SDK update also brings significant improvements, including restoring the ability to capture GPS tracks in the background. This functionality was being blocked in MobileMap 4.x due to Android security restrictions in newer Android OS versions. In MobileMap 5.0 we are using the latest version of the Android SDK, allowing us to overcome this limitation. Now you can now continue to collect GPS lines and polygons even when MobileMap is put into the background due to screen timeouts or opening of other apps. This makes the capture of GPS lines and polygons much more robust as a feature can be started, the screen can be turned off and the user can navigate their route with confidence.
The adoption of the ArcGIS Sync framework requires that all ArcGIS Feature Services used with MobileMap are ‘sync enabled’. Previously, (MobileMap 4.x) did not require Feature Services to be sync enabled, although many clients did sync enable their services for compatibility with Esri COTS applications like Field Maps.
MobileMap 5.0 only supports one Feature Service at a time. In MobileMap 4.x and earlier, multiple Feature Services could be used at the same time. While this is an uncommon workflow, some users found this useful, especially for including reference data like ownership boundaries or roads. Because MobileMap 5.0 uses ArcGIS offline geodatabases and sync framework, there is a one-to-one relationship between offline geodatabases and Feature Services. MobileMap 5.0 supports a single offline geodatabase and thus supports a single service at one time. As an alternative to multiple Feature Services, some clients may need to transition read-only layers like to ownership boundaries or roads to Shapefiles or TPKs, or to include these as additional layers in the operational Feature Services.
The configuration process has been streamlined in 5.0 to combine a few steps:
MobileMap 4.x
Sign in
Select Feature Service(s)
Initialize database
Set download parameters (optional)
Download
MobileMap 5.x
Sign in
Select Feature Service
Configure Offline Geodatabase Parameters (optional)
Download
Specifically, the following changes have been implemented in 5.0:
The optional ‘Download Parameters’ user interface in MobileMap 4.x has been renamed to ‘Configure Offline Geodatabase Parameters’ and included as a step when generating the offline geodatabase. These parameters remain the set for the lifespan of the offline geodatabase. ArcGIS Desktop users can think of this as setting a ‘definition query’ on the offline geodatabase. If the parameters must be changed to include different or additional data, the geodatabase will by synced and recreated with the new parameters. This is similar to the process in 4.x where the database needed to be reinitialized when changing download parameters.
The MobileMap 4.x step ‘Initialize Database’ is no longer needed and has been removed. This step is now inherent in the process of generating the offline geodatabase.
The MobileMap 4.x step ‘Download' is now included in the process of generating the offline geodatabase - the initial geodatabase will contain all of the feature that meet the provided parameters. The ‘Download’ step is only needed when new data should be downloaded to a device after an initial configuration.
A new Action List item ‘OFFLINE GEODATABASE INFO’ has been included in MobileMap 5.0. This feature displays the details of the current offline geodatabase and allows for the explicit deletion of the currently downloaded Geodatabase.
In additional to the streamlined configuration process described above, the following enhancements have been included in MobileMap 5.0:
Improved credential management
In MobileMap 4.x, users frequently needed to sign in to ArcGIS when uploading and downloading data, downloading base maps, or switching Feature Services.
MobileMap 5.0 streamlines sign in by supporting saved passwords from the Chrome browser password manager
MobileMap 5.0 stores user credentials and prevents the need to sign in again for the length of the credential lifespan.
MobileMap 5.0 supports explicitly signing out of ArcGIS. This may desirable when handing off a device to another user, or when you don’t plan to use MobileMap for some time and want to make sure that you are signed out. To sign out click the “LOGOUT OF ARCGIS” button from the Actions Menu.
GPS background tracking
As described in the Overview section, background location tracking is now available in MobileMap 5.0. When recording Tracks or using GPS to capture any line or polygon, MobileMap will still be able to properly collect location data even when MobileMap is in the background (screen locked, other app open, etc.).
Database Backup and Restore
MobileMap 4.x used a custom file formats for storing new and modified data
The typical format was JSON, in which backup data were stored in a text file using JSON format, and data managers needed to copy/paste data into Feature Service REST enpoints when data recovery was needed.
An optional SQLite database backup contained all data, but was even more challenging to use for data recovery, typically involving WSG support.
MobileMap 5.0 uses Esri offline geodatabases and supports data recovery using two approaches
Copy of the full offline geodatabase to a PC and use of ArcGIS Pro to sync the offline geodatabase with the Feature Service. This process is documented by Esri as the data recovery method for Field Maps
MobileMap 5.0 makes regular backups of new and modified data, just like MobileMap 4.x did, but using a new file format - ArcGIS geodatabase delta files. These delta files are simplified offline geodatabases that only contain the modified data, and are the same files that the sync process sends to the Feature Service when performing a sync. Although Esri does not currently have an end-user tool for uploading data from these Delta files, WSG has developed a process and is working to create an easy-to-use tool in InventoryManager to facilitate incremental data recovery via database delta files.
Vertex Editing
Deleting vertices on a line or polygon is now performed using a double tap instead of a long press.