| Table of Contents |
|---|
Why
...
When I collect more than 20 trees and then try to scroll to the top of the tree list to view the first few trees, they are gone. I know the trees are being saved because when I upload them I can see them in InventoryManager and in ArcGIS Online, but when I reopen the tree list for that plot I can’t display the first trees.
Most likely this is because you had collected more than 20 trees. There is a setting in MobileMap to optionally limit the amount of trees that are displayed. The default is 20, which works well for typical scenarios because a typical BAF plot will have 5-10 trees for most foresters, while a 100% Tally will not get bogged down trying to handle scrolling of potentially hundreds of trees. To fix this, change the max tree rows to display setting near the bottom of the Trees settings (Settings > MobileMap Cruise > Trees > Maximum Number of Tree Rows.
Why does MobileMap freeze with message "backing up database" After closing tree list?
When closing the tree list MobileMap freezes with message "backing up database" and a spinning circle. I have to force close the app and restart. No data is lost, but once the problem starts happening it seems to happen all the time. Uploading my data seems to help for a while.
This is typically caused by insufficient disk space. MobileMap tries to make a backup of all features that have been created or edited since your last upload. After a big data collection, the backup file can be large. After many days of collection, there can be a large number of files. Since your device had limited space when we set it up on Monday, this is likely the cause. Deleting files to free up space should resolve this issue. As a workaround you can disable the automated backup in settings (Settings > MobileMap Cruise > General > Database Backup Interval) by setting it to ‘Never’ but this is not recommended as it could put your data at risk if your device is damaged prior to backup.
What ArcGIS Online User Type do I need in order to use MobileMap?
Follow this link to see the available user types https://www.esri.com/en-us/arcgis/products/arcgis-online/buy. MobileMap requires Editor user type to enable create/edit/delete of features. Many users prefer to purchase the the Field Worker user type at the higher price so they can access other Esri applications such as Collector (soon to be replaced by Field Maps), Survey123, Dashboards, etc. The Field Worker user type is not needed, however, if you only plan to use MobileMap (and WSG InventoryManager).
Why does my Base Map disappear when I zoom in?
I used the Download Basemaps tool and download a TPK file, then copied it into the TPK folder in my project directory. The base map displays fine when I am zoomed out, but when I zoom in the map completely disappears. I was hoping it would just get blurry if I zoomed in further than the resolution of the base map.
The Download Basemaps tool uses Esri’s base map services and specifically the export image endpoint. For some reason, Esri decided to set the maxScale parameter within the TPKs it produces. While we have suggest that this is not the expected or desired behavior, that setting persists. This means that if you selected zoom level L15 when downloading the base map, the image completely disappears (won’t display) when you zoom to level 16 or greater. There is a workaround (see below), but it is complex and can’t be completed within MobileMap. Where possible, try to zoom in to as small of an extent as possible, and select a zoom level that meets your needs in the field (e.g., L16). In our experience, downloads greater than 100MB are seldom successful, so you may need to accept a lower zoom level, or break your base map into multiple smaller extent base maps.
TPK maxScale workaround:
Copy TPK to a PC
Rename file from *.tpk to *.zip then unzip the file
Open the file \servicedescriptions\mapserver\mapserver.json in a text editor
Search for all instances of “mapScale”, and change any non-zero mapScale values to 0
Save mapserver.json
Select all of the folders that were in the TPK
Rezip all of the folders that were produced when unzipping the original file. The re-zip must be done without compression. This is the trickiest step, as the default windows zip tool cannot do this. You will need a zip utility like 7-zip that has the option to simply archive with no compression.
Rename file back to *.tpk
Copy TPK back to the appropriate folder in your MobileMap directory on your mobile device
Can I use the same base map TPK in MobileMap and Esri’s Field Maps?
My organization uses Field Maps in addition MobileMap. Both apps use base maps in TPK format and I would like to be able to make a single TPK file and use it in both apps. Is this possible and if so, how do I do that?
The short answer is that you cannot use the same TPK base map file with both Field Maps and MobileMap. The main reason for this is Android security - Android creates silos to protect apps from accessing other apps data. MobileMap uses a specific file structure and access data in that file structure is possible because the user grants permission when selecting their data directory in MobileMap. Field Maps using a different directory structure which it has permission to read and write data. It is possible to create a TPK and save it into two locations, one for Field Maps and another for MobileMap. This approach may be the most efficient way to create base maps, as it may cut down on the processing time for building TPKs. It will, however, require twice the data volume of the TPK since it will be stored in two different locations.
If this poses a significant impact to your organization please contact our team and we can explore options for enhancing MobileMap to
Why can’t I see any base maps in MobileMap?
I used the Download Basemap tool and it seemed to work as expected - displayed a message that base map had been downloaded, but I don’t see my base map - just a blank screen. How can I get my base map working?
There are a number potential causes for this issue. Use the check list below to help resolve the issue:
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: Application Licensing
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’.
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’.
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.
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
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
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. WSG 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.
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 for 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.
Why does MobileMap display a “Licensed for Developer Use Only” message?
...
is MobileMap displaying an error when installing on Android 14?
I installed MobileMap 4.4.x on a new tablet running Android 14. During the installation, MobileMap displays an error indicating that MobileMap was built for an older version of Android. Everything seems to install and run fine. Is it OK to use?
This is a known issue and is caused by the version of the Android SDK that is used in MobileMap 4.x. When installing MobileMap 4.x on Android 14 devices (or when a device upgrades to Android 14) users will receive a warning indicating that MobileMap was built for an earlier version of Android. Users can close this warning and use MobileMap as expected. This issue will be addressed with the MobileMap 5.0 release.
Why can’t I can’t see the first trees I collected when I collect more than 20 trees?
When I collect more than 20 trees and then try to scroll to the top of the tree list to view the first few trees, they are gone. I know the trees are being saved because when I upload them I can see them in InventoryManager and in ArcGIS Online, but when I reopen the tree list for that plot I can’t display the first trees.
Most likely this is because you had collected more than 20 trees. There is a setting in MobileMap to optionally limit the amount of trees that are displayed. The default is 20, which works well for typical scenarios because a typical BAF plot will have 5-10 trees for most foresters, while a 100% Tally will not get bogged down trying to handle scrolling of potentially hundreds of trees. To fix this, change the max tree rows to display setting near the bottom of the Trees settings (Settings > MobileMap Cruise > Trees > Maximum Number of Tree Rows.
Why does MobileMap freeze with message "backing up database" After closing tree list?
When closing the tree list MobileMap freezes with message "backing up database" and a spinning circle. I have to force close the app and restart. No data is lost, but once the problem starts happening it seems to happen all the time. Uploading my data seems to help for a while.
This is typically caused by insufficient disk space. MobileMap tries to make a backup of all features that have been created or edited since your last upload. After a big data collection, the backup file can be large. After many days of collection, there can be a large number of files. Since your device had limited space when we set it up on Monday, this is likely the cause. Deleting files to free up space should resolve this issue. As a workaround you can disable the automated backup in settings (Settings > MobileMap Cruise > General > Database Backup Interval) by setting it to ‘Never’ but this is not recommended as it could put your data at risk if your device is damaged prior to backup.
What ArcGIS Online User Type do I need in order to use MobileMap?
Follow this link to see the available user types https://www.esri.com/en-us/arcgis/products/arcgis-online/buy. MobileMap requires Contributor user type to enable create/edit/delete of features. Many users prefer to purchase the the Mobile Worker user type at the higher price so they can access other Esri applications such as Field Maps, Survey123, Dashboards, etc. The Mobile Worker user type is not needed, however, if you only plan to use MobileMap (and WSG InventoryManager).
Why does my Base Map disappear when I zoom in?
I used the Download Basemaps tool and download a TPK file, then copied it into the TPK folder in my project directory. The base map displays fine when I am zoomed out, but when I zoom in the map completely disappears. I was hoping it would just get blurry if I zoomed in further than the resolution of the base map.
The Download Basemaps tool uses Esri’s base map services and specifically the export image endpoint. For some reason, Esri decided to set the maxScale parameter within the TPKs it produces. While we have suggested that this is not the expected or desired behavior, that setting persists. This means that if you selected zoom level L15 when downloading the base map, the image completely disappears (won’t display) when you zoom to level 16 or greater. There is a workaround (see below), but it is complex and can’t be completed within MobileMap. Where possible, try to zoom in to as small of an extent as possible, and select a zoom level that meets your needs in the field (e.g., L16). In our experience, downloads greater than 100MB are seldom successful, so you may need to accept a lower zoom level, or break your base map into multiple smaller extent base maps.
TPK maxScale workaround:
Copy TPK to a PC
Rename file from *.tpk to *.zip then unzip the file
Open the file \servicedescriptions\mapserver\mapserver.json in a text editor
Search for all instances of “mapScale”, and change any non-zero mapScale values to 0
Save mapserver.json
Select all of the folders that were in the TPK
Rezip all of the folders that were produced when unzipping the original file. The re-zip must be done without compression. This is the trickiest step, as the default windows zip tool cannot do this. You will need a zip utility like 7-zip that has the option to simply archive with no compression.
Rename file back to *.tpk
Copy TPK back to the appropriate folder in your MobileMap directory on your mobile device
Can I use the same base map TPK in MobileMap and Esri’s Field Maps?
My organization uses Field Maps in addition MobileMap. Both apps use base maps in TPK format and I would like to be able to make a single TPK file and use it in both apps. Is this possible and if so, how do I do that?
The short answer is that you cannot use the same TPK base map file with both Field Maps and MobileMap. The main reason for this is Android security - Android creates silos to protect apps from accessing other apps data. MobileMap uses a specific file structure and access data in that file structure is possible because the user grants permission when selecting their data directory in MobileMap. Field Maps using a different directory structure which it has permission to read and write data. It is possible to create a TPK and save it into two locations, one for Field Maps and another for MobileMap. This approach may be the most efficient way to create base maps, as it may cut down on the processing time for building TPKs. It will, however, require twice the data volume of the TPK since it will be stored in two different locations.
If this poses a significant impact to your organization please contact our team and we can explore options for enhancing MobileMap to
Why can’t I see any base maps in MobileMap?
I used the Download Basemap tool and it seemed to work as expected - displayed a message that base map had been downloaded, but I don’t see my base map - just a blank screen. How can I get my base map working?
There are a number potential causes for this issue. Use the check list below to help resolve the issue:
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: Application Licensing
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’.
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’.
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.
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
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
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. WSG 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.
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 for 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.
Why does MobileMap display a “Licensed for Developer Use Only” message?
I opened MobileMap today and I now see the message “Licensed for Developer Use Only” as a watermark in the corner of the map. I have never seen this before and don’t know how to make it go away.
...
e. Select the folder that holds map caches, typically this is called “MobileMap” and is on the SD Card
f. Select “Done”
e. Go to Actions > Use the Select Map Cache tool to re-load map cache
Why can I not select a Data Directory ?
...
Check your username in the Authentication Setting and make sure there is not an extra space after your username in the setting. Some tablets and phones automatically add a space after words, including usernames and emails. To fix this open MobileMap Authentication Settings and the ArcGIS Username setting. Backspace over the extra space.
Why am I getting an upload error in MobileMap?
...
Upload report show errors on one or more features in MobileMap.
If you get an upload error message, like this message below, while trying to upload your data from MobileMap:
...
If you try adding the data from AGOL using the JSON backup text file you would get this error message:
...
Most likely there is a duplicate field name in the data Here are a couple of things to try:
Check your WiFi connection and try to upload again. CAUTION: This may cause duplicate data if you are creating new features, like trees. Be sure to QC your data after you upload.
Try to add/update the data through Rest Services in AGO using the JSON backup text file. This can help identify if there are data quality issues. You might get an error message like this:
...
Most likely there is a duplicate field name in the data being uploaded causing this error. Duplicate field names can be caused by adding the incorrect field names into some the MobileMap settings. This example below shows two ‘Observer' fields. One with a capital ‘O' and one with a lowercase 'o’:
...
To learn more about data backup and recovery go to https://masonbruce.atlassian.net/wiki/spaces/MD/pages/262212/MobileMap+Data+Backup+Recovery+and+Export#Overview
...
An error occurred. Data may not have been uploaded as expected…
...
One scenario that can create this error is if you accidentally have two feature services selected - the one you are using to collect data and one that is NOT actually being used. While it is possible to utilize two (or more) feature services at the same time, they must all be initialized at the same time. When you select more than one feature service in the ‘Select Feature Services’ you will be presented with a warning message. If you ignore this warning but do not initialize the database, you may experience the error message above.
To resolve this error, open the Actions Menu (third tool button) and choose ‘Select Feature Service’. Inspect the list looking for multiple checked boxes. If you find that one or more feature services was selected in error, uncheck that checkbox and try to upload again.
Another scenario is there is a bad piece of data, or data without geometry, collected. This is more common when collecting point data and not as common when cruising where you are not creating points as you go. One option here is to close MobileMap and reopen from app icon. Then upload again. CAUTION: This may create duplicate data. QC your data carefully.
If this does not resolved the upload error please contact your MobileMap support or submit a ticket via support@woodlandsg.atlassian.net.
...
If you published your feature service from ArcPro either overwriting and an existing service or publishing to a new service from an ArcPro map that was used previously to publish a feature service, try publishing from a fresh ArcPro project and publish to a new feature service not overwriting the existing one. Not ideal, but seems to resolve the issue. Clearing the cache in ArcPro or starting from a fresh map resolves the issue occasionally, but not consistently.
...
“… BUG-000144318 - When you publish a layer from ArcGIS Pro to ArcGIS Online that has default values set on at least one field and there are existing features the default values will not show up in ArcGIS Field Maps web app Smart Form Templates.
They[Esri] informed me of the following workaround:
You can export a FGDB in ArcGIS Online from the hosted feature layer that has these default values setup and then publish a new hosted feature layer copy from this FGDB. This copy will not exhibit the behavior. Note that this will be a distinct layer and will not have a service definition. Meaning that you can't overwrite it from ArcGIS Pro like the original layer.”
MobileMap Crashes When Editing Features or Saving Tree Table When Using a Settings File Copied from Other Service/Tablet
The settings file is a great way to ensure consistency with MobileMap configuration among your cruisers/field staff. Please see our MobileMap: Settings page for a detailed descriptions of the settings within MobileMap. Settings files can be published with the feature service or a side-loaded text file on the tablet. Many organizations share settings text files among user tablets and cruises and occasionally this leads to incompatible settings files being used and this can cause MobileMap to crash at various points in data editing. Here are some troubleshooting tips for a potentially incompatible settings file:
IMPORT SETTINGS and reset to defaults using the circle refresh arrows
Try editing a feature or the trees depending on what is causing the crash
Turn on MobileMap Cruise manually
The tree table may not be readable due to no tree ignore fields, but you can test the save at least
If nothing crashes start adding back in settings testing in between each such as:
Hidden Fields
Read-Only
Configurable Defaults if used
GPS Tracking Turns Off When Tablet Screen is Locked
The GPS tracking mode, in MobileMap, will stop tracking when the tablet screen is locked. This issue is related to increased security in newer Android versions. Google doesn’t want apps to track you in the background without asking your permission first. We are working to resolve this with a software update for MobileMap. Until then, you might find it useful to use a touch pocket protector and keep your screen open/unlocked like this one https://play.google.com/store/apps/details?id=biz.obake.team.touchprotector&hl=en_US&gl=US.
Note that although the touch protector is useful for locking the screen to prevent unwanted map taps, it does not help to preserve the battery, like shutting of the screen would.
For more information on GPS Tracking see https://woodlandsg.atlassian.net/wiki/spaces/MD/pages/262196/MobileMap+GPS+Data+Collection+and+Editing#Tracks-(Travel-Path%2C-Bread-Crumbs) .
MobileMap Does Not Recognizing Non-Standard Field Names
MobileMap uses default field names for fields as Unique_ID, Parent_ID. If you are using non-standard field names, even lowercase for these fields these will need to be changed in the settings on the tablet or in the settings imported from the feature service or settings text file. For a detailed list of defaults, please refer to the MobileMap settings on at least one field and there are existing features the default values will not show up in ArcGIS Field Maps web app Smart Form Templates.
They[Esri] informed me of the following workaround:
You can export a FGDB in ArcGIS Online from the hosted feature layer that has these default values setup and then publish a new hosted feature layer copy from this FGDB. This copy will not exhibit the behavior. Note that this will be a distinct layer and will not have a service definition. Meaning that you can't overwrite it from ArcGIS Pro like the original layer.”
MobileMap Crashes When Editing Features or Saving Tree Table When Using a Settings File Copied from Other Service/Tablet
The settings file is a great way to ensure consistency with MobileMap configuration among your cruisers/field staff. Please see our MobileMap: Settings page for a detailed descriptions of the settings within MobileMap. Settings files can be published with the feature service or a side-loaded text file on the tablet. Many organizations share settings text files among user tablets and cruises and occasionally this leads to incompatible settings files being used and this can cause MobileMap to crash at various points in data editing. Here are some troubleshooting tips for a potentially incompatible settings file:
IMPORT SETTINGS and reset to defaults using the circle refresh arrows
Try editing a feature or the trees depending on what is causing the crash
Turn on MobileMap Cruise manually
The tree table may not be readable due to no tree ignore fields, but you can test the save at least
If nothing crashes start adding back in settings testing in between each such as:
Hidden Fields
Read-Only
Configurable Defaults if used
GPS Tracking Turns Off When Tablet Screen is Locked
The GPS tracking mode, in MobileMap, will stop tracking when the tablet screen is locked. This issue is related to increased security in newer Android versions. Google doesn’t want apps to track you in the background without asking your permission first. We are working to resolve this with a software update for MobileMap. Until then, you might find it useful to use a touch pocket protector and keep your screen open/unlocked like this one https://play.google.com/store/apps/details?id=biz.obake.team.touchprotector&hl=en_US&gl=US.
Note that although the touch protector is useful for locking the screen to prevent unwanted map taps, it does not help to preserve the battery, like shutting of the screen would.
For more information on GPS Tracking see https://woodlandsg.atlassian.net/wiki/spaces/MD/pages/262196/MobileMap+GPS+Data+Collection+and+Editing#Tracks-(Travel-Path%2C-Bread-Crumbs) .
MobileMap Does Not Recognizing Non-Standard Field Names
MobileMap uses default field names for fields as Unique_ID, Parent_ID. If you are using non-standard field names, even lowercase for these fields these will need to be changed in the settings on the tablet or in the settings imported from the feature service or settings text file. For a detailed list of defaults, please refer to the MobileMap settings https://woodlandsg.atlassian.net/wiki/spaces/MD/pages/360559/MobileMap+Settings#(GEAR-ICON-ON-MOBILEMAP-HOME-DISPLAY).
The setup steps in MobileMap play an important role when changing the default field names on settings such as Unique_ID, Parent_ID, Stand_ID, Plot_ID, etc. After importing settings in MobileMap and MobileMap Settings open automatically. This ensures the settings are read by MobileMap. When changing default field names, especially, it may be necessary to also close the MobileMap app after importing the settings and before the initial data download. It has been noted in an few instances that the settings do not “stick” until the following steps are taken:
Initialize Database
Import Settings
Close MobileMap settings
Close MobileMap and Reopen from App Icon
Download Data
Tree Rows Hidden or Missing
This may occur during a Standard Cruise when collecting large numbers trees or during a Check Cruise when copying trees into Check Cruise due to the keyboard hiding the last few trees in the list or the number of tree rows is set too small. See the https://woodlandsg.atlassian.net/wiki/spaces/MD/pages/360559/MobileMap+Settings#(GEAR-ICON-ON-MOBILEMAP-HOME-DISPLAY).
The setup steps in MobileMap play an important role when changing the default field names on settings such as Unique_ID, Parent_ID, Stand_ID, Plot_ID, etc. After importing settings in MobileMap and MobileMap Settings open automatically. This ensures the settings are read by MobileMap. When changing default field names, especially, it may be necessary to also close the MobileMap app after importing the settings and before the initial data download. It has been noted in an few instances that the settings do not “stick” until the following steps are taken:
...
Initialize Database
...
Import Settings
Close MobileMap settings
...
Close MobileMap and Reopen from App Icon
...
Settings#MobileMap-CRUISE to help adjust the visibility of the tree list.
Maximum Number of Tree Rows
Select the maximum number of tree rows to display at any one time (fewer rows improves performance)
Tree List Keyboard Offsets
Optional offsets to prevent keyboard from hiding tree rows at the bottom of tree list. Only need on some devices where keyboard hides last trees in list. If a single value is listed, it will be used in both Standard and Check Cruise modes. If 2 values are listed as a comma separated list (e.g.,200,400) then the first value will be used in Standard mode and the second value in Check Cruise mode.
MobileMap Crashes When Zoom/Pan Map
This could be related to a corrupt TPK. A quick way to check this is to turn off all TPKs. Use the Select Layer Display Properties and uncheck all the layers ending in *.tpk. If this resolves the issue turn on the TPKs one a time to determine which one is the culprit.