...

1. Verify that MobileMap licensed - MobileMap must be licensed to display base maps. If it is not licensed, or if the license has expired or is not valid, you should see a brief popup message when MobileMap starts up that indicates that the license was not found or is not valid. The best way to check, however, is to use the license tool (Actions > License Device). At the top of this tool you should see a message indicating the license status. If the license has expired simply re-submit to refresh your licenses. If you have never licensed your device, follow instructions here MobileMap: Installation and Licensing and hereMobileMap Licensing

2. Verify that the data directory is correct - Base maps are stored in a data directory, typically on a MicroSD card, and MobileMap must have access to that directory. Use the Select Data Directory tool (Actions > Select Data Directory) to select the data directory. See instructions here MobileMap: Installation and Licensing. Note that the directory selected during this process should be the MobileMap root directory, and should not contain TPK or Shapefiles directly within it. The MobileMap root directory is typically named ‘MobileMap’ and should have a subfolder named ‘default’ and will likely have other folders like ‘Export’ and ‘Photos’.

3. Verify that your MobileMap folder structure is correct. MobileMap uses project or map cache folders which can be named however you want, but we recommend avoiding spaces or special characters in folder names. Project folders are found in the MobileMap root directory. Each project folder will have subfolders including ‘TPK’ and optionally ‘SHP’.

4. Verify that the base map you downloaded was successfully copied into the correct subfolder. The Download Basemap tool saves all downloaded TPK files into the devices Download folder. This is due to some limitations on file saving on some devices. This requires users to manually copy downloaded files to the correct TPK folder in their desired project folder. Use your devices file manage (e.g., ‘My Files’ on Samsung, ‘Files’ on Google Pixel, etc.) to copy files between folders. For example, if you are working on a project called ‘MyProject’, you will copy the TPK that you download from internal storage/Download → SD Card/MobileMap/MyProject/TPK.

5. Verify that the correct project has been selected. Use the Select Map Cache tool select the project or map cache where you saved your TPK. See instructions here MobileMap: Basic Operation

6. Verify that the TPK is enabled for display in display properties. Use the Select Layer Display Properties and verify that the TPK is visible in the list (should be near the bottom or the layers list) and that the checkbox is checked. See instructions here MobileMap: Basic Operation

7. Verify the extent of the base map you downloaded. MobileMap uses the first loaded map cache to set the maximum map extent. If the first loaded base map (e.g., TPK) is small and not in your area of interest, you will be unable to pan the map to your current extent, thus your new base map will not be visible. MB&G recommends creating a single large area, low resolution base map and storing it in the default folder (e.g., SD Card/MobileMap/default/TPK) which can be used by MobileMap to set a large map extent when it is loading base maps.

8. Verify the zoom level of the base map you loaded. Base maps downloaded within MobileMap have a maximum scale or zoom level applied to them. See the question Why does my Base Map disappear when I zoom in? for more details on this problem. If you have made it to this step, then it is possible that you are simply too far zoomed in for your base map to display. Try zooming out - way out - and see if your base map shows up. If so, use the approaches described above or in this document MobileMap: Base Map Creation and Reference Datafor MobileMap to address this issue.

If you have gone through each of these verification steps and still do not see your map, please reach out to our support team. It will help us resolve the the issue if you can provide screenshots of your folder structure, the Select Map Cache tool, the Select Layer Display Properties tool, etc. It may even be helpful to upload a copy of your TPK file when submitting your support request.

...

Make sure the files under each folder, TPK and SHP are not buried in another TPK folder.

...

Why did MobileMap create duplicate data (e.g., stands/plots/trees)?

I uploaded data from MobileMap and now have duplicate data. Why did this happen, how can I remove the duplicates and how can I prevent this from happening again in the future?

While this situation is very uncommon, there are a few scenarios where this can occur. The good news is that if/when this problem occurs, it does NOT result in any loss of data, only additional data. There can, however, be downstream effects if duplicate data are then used to compile timber volumes, etc.

1. The most common cause of duplicate data is a bad internet connection during upload. In this scenario, MobileMap uploads data that were created (not just updated) on your mobile device. These records are new, thus are sent to the ‘addFeatures’ endpoint of the feature service. If MobileMap sends the data, but the internet connection is broken before a response is received from the service, MobileMap will not know that the data were successfully received. When this happens, MobileMap has to assume that the data were not received, so it keeps these data in the list of features to upload on the next attempt. When the upload happens the next time, these data are sent again, creating duplicates. If they receive the response from the server on this second attempt, then MobileMap updates their status and they are no longer queued for upload. In this example, you would have 2 copies of each feature.

2. There have been a few reports over the years of duplicates being created when an unusual data issue is encountered when configuring or testing a new feature service or settings. In these cases, the data were saved by the server, but the server returned an unexpected response, such as an error message describing an unexpected SQL database error in the backend of a Portal implementation. In these cases the data have been saved correctly, but the error message causes MobileMap to believe that the data were not saved. Thus, MobileMap resends the data on the next upload

To determine which scenario above has caused the problem you are seeing, start by ensuring a strong WiFi connection and then re-upload within MobileMap. Note that may create another duplicate set of data. In scenario 1 above, if there are failed uploads on the system, they will successfully uploaded and thus no longer queued for upload. In this case the upload problem will be solved, but data will need to be cleaned up to remove duplicates (see below). In scenario 2 above, the data problem may still exist - and this should be seen in the upload report in the form of an error for one or more layer.

If the problem does still exist (scenario 2) then it can be helpful to export the MobileMap database and try to manually add the data to the feature layer. Using this manual approach, you may see a more detailed error that will help you understand what the data problem is and how to resolve it. If not, reach out to MB&G support team to help resolve.

Once the source of the issue has been resolved, the duplicates will need to be removed. Start detecting the duplicates by looking for features with exact matches in their Unique_ID field. You can review these using ArcPro or other tools, or using a ‘find duplicates’ tool that MB&G can enable on your InventoryManager (or other Spatial CMS) site. When enabled, this tool performs a statistical query of a feature layer to find all Unique_ID values with more than one instance, and retrieves the OBJECTIDs for all but the last instance. These OBJECTIDs can then be used to delete the duplicates.