Overview of MobileMap 5.0 Changes

MobileMap 5.0 represents a significant evolution for the MobileMap application. Many of the changes that have been made, however, are under-the-hood rather than changes that affect user interfaces or workflows. MobileMap 5.0 leverages updated versions of the ArcGIS and Android Software Development Kits (SDKs). This helps to ensure that MobileMap complies with enhanced Android security measures and updated Android and ArcGIS capabilities.

...

1. 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.

2. 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.

3. 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.

4. 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.

MobileMap 5.0 Enhancements

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.).

Other Changes in MobileMap 5.0

• 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.

...