Before You Begin

• This guide is intended to support the process of downloading, installing and configuring MobileMap for licensed MobileMap users.  If at any time in this process you need help to complete a step, or experience an error that you cannot resolve, please contact MB&G's software support at:
  • Support Email: software@masonbruce.com
  • Support Phone: 503-290-0542
• Make sure that you created a 6 digit license request code (e.g., a1b2c3) at https://mobilemap.mbgapplications.com/my-licenses. If you need asstistance contact MB&G's software support using the methods above.
• If you have a previous version of MobileMap on your tablet:
  • Please make sure that all data have been uploaded.  If you experience issues uploading data, please export your current database using Actions > 'Export Database', and contact MB&G to arrange for your data to be recovered. 
  • Once you have your device code and all data have been uploaded (or if there are no data to upload), you MUST uninstall the previous version of MobileMap before proceeding.  To do this, open up Android Android Settings (gear icon) then go to 'Apps'.  Scroll down until you see MobileMap and select it, then tap on 'Uninstall'.
• You should now be ready to download and configure MobileMap!

Download and Install MobileMap

• On your tablet, open a browser and navigate to this website: https://mobilemap.mbgapplications.com/downloads
• Go to 'Downloads' tab at the top right of the page
• Tap the link to download MobileMap
• Once the download has completed, locate the downloaded installer file (MobileMap_X.X.X.apk) on your device doing one of the following:
  • Dragging down from the top of your screen to show notifications, one should say something similar to 'MobileMap_X.X.X.apk Download Complete'.  Tap this notification to begin installing MobileMap or Unzipping MobileMap then installing, or
  • Use a file browser (e.g. MyFiles, Astro, etc.) and navigating to Tablet > Downloads, or other location you chose for downloads on your tablet
• During install you may be asked to accept permissions, such as access to media and your location information.  Please select ALLOW to grant access and continue.

• After installation, open MobileMap
• On first open, you will be prompted to select your Data Directory.  The steps to do this are:
  • Actions > SELECT DATA DIRECTORY
    • 
  • Tap SELECT
  • In the user interface that opens, you may need to select ‘Show SD card’ from the ‘more’ menu. Select the MicroSD card from the list on the left and navigate to the MobileMap directory. When you are in the correct directory, tap the link at the bottom which should read ‘SELECT' or something similar.
  • Verify the path in the Select Data Directory popup and, if correct, select ‘Done’

License your device

• Open the License Device tool (Actions > LICENSE DEVICE)
• Select 'Paid License'
• Enter in the 6 letter code that was provided to you by your Organization or MB&G
• Tap 'Submit' 
• MobileMap will communicate with our server, request and receive a license key and then save it in the MobileMap application settings 

• Restart MobileMap (Actions Menu  > CLOSE MOBILEMAP > Confirm then reopen by tapping MobileMap icon ) for the new license to take effect.
• If you do not see any basemaps tap the 'Select Map Cache' icon  to select the map cache you would like to work with.
• Use the 'Select Layers'  tool  to turn layers on/off, to change the symbology of Shapefiles, or to add/remove labels from feature layers.
• Pan and zoom around the map using drag and pinch/spread gestures.
• Use the 'Identify' tool  and tap on Shapefile features to see their attributes.

Proceed to Next Step

• Use the link to proceed to the next step in setup, Configuration and Data Download.

Basic Configuration

• Once MobileMap is installed and licensed, you should be able to see your base map data.  The next step is to connect to the Feature Service that provides the data you will be using, and configure a range of settings. NOTE: Portal users please refer to MobileMap with Portal before proceeding.
• Once you complete this page of the instructions you should be ready to collect field data.  If you run into any issues when completing these steps, please contact MB&G software support at:
  • Support Email: software@masonbruce.com
  • Support Phone: 503-290-0542

Sign In to ArcGIS

• Actions > SIGN IN TO ARCGIS

• Enter your ArcGIS Online Username
• Enter your ArcGIS Online Password
• Tap 'Sign In'
• You should receive a notice stating that you have successfully signed in to ArcGIS

Select and Initialize Your Feature Service

• Actions > SELECT FEATURE SERVICE

• Tap the refresh button to get a list of available Feature Services
• Select one or more the feature services that were created to support your data collection needs by tapping the checkbox to the right of the Feature Service name(s)
• Tap 'DONE' to close
• Actions > INITIALIZE DATABASE
  • If you receive a message stating that you need to Confirm Database Delete and you are installing a new version of MobileMap, then something is wrong.  If you already initialized a feature service MobileMap will prompt you to type 'confirm' to continue
  • After initialization completes, you should see a message stating that the feature service description contains MobileMap settings

Import Settings

Your feature service may have additional settings that require an extra step before downloading your data.

• Actions > IMPORT SETTINGS
  • Tap the 'Feature service' radio button
  • Verify that the Feature Service you are using is selected in the dropdown list and that several settings rows are displayed with their setting, value and a checkbox to 'overwrite' existing settings
  • Tap 'IMPORT' to import these settings
  • You should see a message stating that settings imported successfully
  • Tap 'CLOSE' to finish
• Actions > DONE (closes the Actions menu if it is still open) 

Enter User-Specific Settings

• Open Settings 

• Tap on 'Authentication Settings' - Portal Users please see: MobileMap with Portal

• ArcGIS Username
  • Enter your ArcGIS Online username
• ArcGIS Password
  • Enter your ArcGIS Online password
• Data Model Settings
  • Observer Initials or Name
    • Enter your full name (e.g., John Doe)

Confirm Download Parameters

• Actions > EDIT DOWNLOAD PARAMETERS
  • If you are working with large datasets you may want to edit your download parameteres to filter the data you are downloading, E.g. Tree_Points: WorkArea = 'Portland'

Download Your Data

• Ensure you are connected to WiFi and have a strong signal
• Actions > DOWNLOAD
  • Wait for the download process to complete
  • If you get an error message stating that a token is required, please re-sign in to ArcGIS (Actions > 'Sign in to ArcGIS')
  • Verify the expected number of features that have been downloaded 

Introduction

MobileMap is a native Android, map-centric, field data collection app.  It can be run on a wide range of Android devices, including phones, tablets and data loggers (Anroid 5.0 or higher required).  MobileMap is built from the ground up on Esri mobile technology and is intended for use with ArcGIS (ArcGIS Online or Portal for ArcGIS).  While there are many mobile apps that can be used to collect data, MobileMap is focused on supporting large, high-resolution base maps, enabling efficient collection of high quality field data, and supporting critical workflows for forestry and natural resource management. 

This User Guide is a living document that is updated along with new releases of MobileMap. It is intended to be used by MobileMap users to support common use cases and configurations.  A separate Administrators Guide is available which covers administrative tasks such as publishing Esri feature services or packaging base map data.  Please contact our support team at software@masonbruce.com to suggest improvements to this user guide.

Basic Tablet Operation

Power Device On: Press and hold power button (typically on upper right side of device for Samsung phones and tables, on the lower right face for Juniper Mesa devices).

Power Device Off: Press and hold power button until the option to “Power Off Device” appears. Select the option to “Power Off Device.”

Connect to Wi-Fi: Android Settings (gear icon under Apps on the tablet’s home screen) → Connections → Wi-Fi. Turn Wi-Fi on by sliding switch beside Wi-Fi and select from Wi-Fi networks.

Screen Brightness: Android Settings → Display → Brightness (brighter improves visibility but uses more battery).

Screen Timeout: Android Settings → Display → Screen timeout (typically set to max, set lower to conserve battery).

MicroSD Cards: MicroSD cards contain preloaded map cache data, photos taken while using MobileMap and any data that is exported from MobileMap. To remove the MicroSD card, first remove the tablet from the protective case. 

Samsung S2 - Use supplied ‘poker’ to open the tray containing the MicroSD card on the side of the device (tiny hole along the right edge of the tablet).

Samsung Tab Active 2 – Remove back protective cover and slide MicroSD card from slot.

Samsung Tab A – Open the small cover on right edge of tablet (labeled 'MicroSD'), press down on edge of MicroSD card with fingernail or small thin object, then release to eject card.

Juniper Mesa – Open the compartment on the back and remove the battery.  The Micro SD card slot is under the battery and may be concealed by a black rubber tab.

Map Panel: Main map display and feature interaction area

• Zoom in using one of the following methods:

  • Double tap (1 finger)

  • Spread (2 fingers)

  • Double tap drag down (single finger, on the second tap you hold and drag towards the bottom of the screen)

• Zoom out using one of the following methods:

  • Two finger tap (at the same time)

  • Pinch (2 fingers)

  • Double tap drag up (single finger, on the second tap you hold and drag towards the top of the screen) - this is the only way to zoom out when using a passive stylus (e.g., with gloved hands)
• Pan
  • Drag
• Auto-Pan
  • Use auto-pan tool to continuously pan the map to the current GPS location  

Main Toolbar

Select Map Cache (folding map icon): Allows the user to choose a map cache from the available loaded caches. 

Select Display Layers (layers icon): Allows the user to choose the visible cache and feature layers from the loaded feature service, .tpk, .shp, and .mbtiles files. 

• Operational layers are listed at the top, then Shapefiles, then TPKs (e.g., imagery, topo maps).
• Check or uncheck the box next to the layer to turn it on and off in the map display. To turn all layers on or off at one time, check/uncheck the top box.
• Note that in order to collect data into a feature layer, it must be visible in the map.
• Labels
  • To display labels for a layer select the label field
  • Note that displaying labels can impact performance, especially when there are a large number of features in the layer or Shapefile.  Use with caution.
• Shapefile symbology can be adjusted
  • The outline (point, line, polygon)
  • Fill color (polygon only) can be changed by selecting desired color from drop down (default fill for polygon Shapefiles is clear)

Menu Button (table icon): See below for menu button functionality descriptions.

MobileMap Settings (gear icon): Allows users to change settings and license key.  See the Settings page for more details on Settings. 

ACTIONS MENU

The Actions Menu provices access to a large number of operations (or 'actions').  Some actions are used frequently (e.g., daily) whereas other items are not commonly used by most users.  The most commonly used actions are listed at the top and have larger buttons to make it easier to quickly launch these actions.

• Region='NW'
• Cruiser_ID='JJD'
• Status='Planned'
• Acres>40

Edit Configurable Defaults: Allows user to set defaults for any field that is associated with a domain list (pick list).

Select Data Directory:

In order to enable write access to your file system, Android requires you to grant access to MobileMap for a specific data directory. When you first install MobileMap, you will be prompted to select the data directory. It may be necessary to repeat this process if you add additional MobileMap data directories or if you change your MicroSD card (see note below for more details on changing your MicroSD card).  To do this, choose 'Select Data Directory' from the main menu, then select 'Change'. In the user interface that opens, you may need to select ‘Show SD card’ from the ‘more’ menu. Select the MicroSD card from the list on the left and navigate to the MobileMap directory. When you are in the correct directory, tap the link at the bottom which should read ‘SELECT' or something similar. Verify the path in the Select Data Directory popup and, if correct, select ‘Done’. 

Changing your MicroSD card can cause data access issues on some devices.  If you change your MicroSD card and MobileMap crashes on startup, you will need to re-insall the previous MicroSD card, then unselect this as your data directory, then load the new MicroSD card and select that as your data directory.  The steps to complete this process are as follows:

1. Re-install the previous MicroSD card and restart MobileMap
2. Verify that MobileMap is working and that map data from the MicroSD card
3. Change the data directory to any directory on your internal storage (Actions>Select Data Directory > Change, then select any internal directory - like 'Downloads', then select Done)
4. Remove MicroSD card and replace with the new MicroSD card
5. Change the data directory to desired directory on your MicroSD card (Actions>Select Data Directory > Change, then select the MobileMap directory, then select Done)

Download Basemap: Typically, users are provided with map caches filled with relevant basemap data including imagery and other data. Sometimes, however, it is useful to download smaller basemaps prior to fieldwork. To download a basemap from Esri’s basemap services, sign in to ArcGIS (see above), then select 'Download Basemap' from the main menu. This will open a new interface for selecting the area of interest. Select the desired basemap, zoom and pan to the desired extent, then select the maximum zoom level to download. Larger numbers (e.g. L16) produce higher resolution data than smaller numbers (e.g., L8). This process can be slow and may result in large downloads. Begin with smaller zoom levels (e.g., L10) and smaller extents at first, and increase if needed, and if download time and file size allow. Tap 'Download' to begin the process. The downloaded file will be saved to the device's Download folder and a popup message will notify you when the download is complete. Close the popup window, then use the back button (upper left) to return to MobileMap. Use a file manager application to copy the downloaded TPK to the desired map cache in your data directory, then reload the desired map cache to see the downloaded basemap data. Filenames will include the basemap name and maximum zoom level (e.g., USA_Topo_Maps_L16.tpk.

Export Database: Exports the entire feature database to a local copy on your device storage. Export is only necessary if the user needs to create a local backup copy of collected data. This backup data is stored on the device and can be retrieved by an analyst in the office.

Features to JSON: Exports all data in a currently selected feature layer to a user-provided destination on the tablet in a file format called JSON. These data can be loaded in ArcMap using the JSON to Features tool in ArcMap. This export is not used in typical workflows and is only necessary if a user needs to transfer new or edited data to a desktop computer while an internet connection is not available.

Export Cruise Data: Exports timber cruise data as comma separated value (CSV) files for Stands, Plots, Trees and (optionally) logs. Requires a configuration file (cruiseExportMapping.csv) which maps between the Esri data model and the desired output CSV file format.

Export Settings: Exports a local copy of the current settings as a text file.

Import Settings: When using the ‘Import Settings’ tool, you can choose to import settings from the description field of the currently selected feature service, or from a settings text file saved on the tablet. Importing settings from the currently selected feature service works if and only if the feature service contains valid settings parameters in its ‘description’ field. To import settings from a feature service, select the ‘Import Settings’ tool, then select the 'From feature service ‘description’ field' option, and then press the ‘LOAD’ button. Uncheck any settings you do not wish to import.

There are scenarios where it may be necessary to reset all settings back to their default values.  This happens automatically when a user uninstalls, then re-installs MobileMap.  To reset settings without unintsall/re-install, you can use the Restore Defaults option in the Import Settings tool.  This may be needed if you recently made several adjustments to settings, are experiencing errors during data collection, but can not seem to resolve the issues even after attempting to manually restore the previous settings.  This may also be helpful when testing settings that have recently been added or updated on a feature service.  To restore settings to their default values, select DEFAULTS in the Import Settings dialog, and confirm the warning message by selecting OK.  Note that all settings will be restored to their default values.  This means that even licensing information will be lost.  It is advised that you copy the license device code to the device clipboard prior to restoring settings so that the device can be re-licensed immediately after restoring default settings.

MobileMap supports two main types of navigation: 1) overland travel for walking to selected features during field data collection, and 2) driving directions, when nagivating by vehicle to a field site.  The sections provide details for using both methods.

1) Overland Travel (e.g., Navigating to a Plot)

This short video provides a quick tutorial on field navigation using MobileMap

MobileMap supports navigating to any selected feature through a range of visual cues, direction information (distance and direction) and audio alerts.  When navigating to a feature over large distances, users may wish to combine driving directions (see item 2 below) with field navigation tools documented here.

To navigate to a feature, such as a plot in MobileMap:

• Locate your current location on the map by looking for the blue GPS location indicator.  If you do not see the GPS location indicator, or if the location indicator is grey instead of blue, the GPS is not working or is not able to determine your location.  Verify that locations are allowed (Android Settings > Location > Use Location) and that MobileMap has permission to use location information.  When moving, the GPS location indicator will display a white arrow to indicate the direction of travel.  Note that this is the direction of current travel as determined by the GPS, not the orientation of the tablet.

• Use the identity tool to select a plot (or other feature) and make sure only one feature is selected.

• The selected plot will be highlighted blue.  If you need to confirm that only one plot is selected check plot attribute window to make sure attributes are available for only one plot.

• Once a plot is selected, the distance and direction to the plot will be displayed next to the current Lat/Log values in the upper left corner of the MobileMap.  Note that distance units can be adjusted in settings (Settings > Measurement and Navigation > Linear Measurement Unit)

• Optionally, enable auto-pan to keep the map centered on your current location

• Begin moving towards the plot
• A white arrow will appear in the blue GPS location indicator. The arrow will always point the direction you are travelling.

• Use the white arrow, the distance and direction information, as well as the orientation between your location and the selected plot to help guide you to the plot.  As long as you are moving towards the selected plot, the white arrow should point towards the plot and the distance value will be updated to show a decreasing distance.

Proximity Alert

Users can enable a proximity alert to produce an audio alert (e.g. 'beep' sound) when arriving at a selected feature.  This is very useful when navigating to inventory plots, as it can help remove bias when determining the location of plot center.  When the device beeps, you are at plot center.

To enable proximity alerts:

• MobileMap general settings (gear icon)
• Measurement and Navigation -> Enable Proximity Alert

To change Proximity Alert Distance:

• Enter the distance at which an alert should sound into the Proximity Alert Distance setting.  This distance is in the linear measurement units which MobileMap is currently using.  Typically values are between 20 and 30 feet.

To change the Alert Sound:

• Go to the Tablet's Android Settings (home screen of tablet, gear icon) and change the default notification sound (Sound > Default notification sound).
• Verify that the device volume is set to maximum, and that it is not set to vibrate or 'Do not disturb' mode.

2) Driving Directions

MobileMap supports retrieving driving (or walking via roads) directions accessing ArcGIS Online's routing service.  This functionality requires a user to be a) have internet (e.g., Wi-Fi) connection and b) be currently signed in to ArcGIS Online via MobileMap.  Once the directions have been calculated, the spatial path of travel to the user's destination will be displayed on the screen and turn by turn directions can be displayed.  The route and directions will be automatically stored on the device and thus can be used offline. Note: if your organization uses Portal for ArcGIS, driving direction functionality is not available.

Navigate to a Point or Feature Using MobileMap

• Make sure you are logged in to ArcGIS Online via MobileMap and have internet connection (Portal for ArcGIS organizational accounts do not support driving directions)
• Use the identity tool and select a feature for your destination

• Select the 'Get Directions' on the feature identity results window to calculate directions to your destination

• The route from your current location to your destination will be displayed on the map screen as a blue highlighted path

• To display the turn-by-turn directions, select the 'Get Directions' icon (now highlighted blue, which indicates MobileMap has a stored direction)

• To hide the spatial direction route from the map, select "Hide Route" on the Directions pop-up window
• To delete the route, select "Delete Route' on the Directions pop-up window
• MobileMap stores the most recently created route (only one route at a time) for offline use

The query and collect toolbar includes (from left to right) an 'identif'y' button, a 'draw' button, a 'GPS collect' button, and an 'edit' button.

Identify: The 'identify' button allows the user to query the attributes of existing features (read-only).

Vertex Editing

Vertex editing allows a user to manually adjust one or more vertices to re-shape an existing spatial feature's geometry.  The main steps for editing vertices include selecting a feature for editing, selecting Vertex Editing, adjusting one or more vertices, optionally deleting one or more vertex, saving the vertex edits.

Selecting the Feature for Editing

Once the polygon is created. Select ‘Select Layer for editing’ option is the tools menu on the right side to open editing option. This will list all feature types available to edit. Select the polygon layer you must edit. In this case it is ‘Stands’.

*Note that you can also select an old record to edit by tapping on the polygon.

Editing Vertices

Once you have a layer to edit, the attribute of that record will pop up. Select the pencil tool again in this menu and select ‘Edit vertices’ as shown below. This will give you the option to only edit the vertices of this polygon.

After you select ‘Edit Vertices’. The selected polygon will turn red and all vertices will show as points attached to the polygon. You will also see a green check mark and a red cross on the top left of screen. (Shown below)

Tap on the vertex you want to change, don’t’ let go of your finger from the screen, simply drag it to the location you want and let go. Below is an example of what it would look like once you expand all the vertices outwards.

*Note that vertices can be dragged anywhere on the map.

Tap on the green check mark to complete the edit. This will get rid of the red polygon and the screen now will only have a green highlighted polygon with current selected vertex locations.

Deleting Vertex

Following the same process for editing, one can delete the vertex as well to reduce the size of the polygon. Go through initial steps of highlighting your polygon. Change the vertex locations as you want. To delete a vertex, simply press on the vertex location for a fraction of a time longer than you would for editing and let go. This will delete the vertex.

As shown below, the vertex is deleted. Tap on green check mark to finish the sketch and a new polygon with less vertices is now formed. You can also tap on the red cross to redo the edit.

Copying

This is the workflow for copying the geometry and (optionally) attributes from a ‘parent’ feature to ‘child’ feature.

    1. Select the parent polygon using the edit tool (small pencil) 

    2. Select the copy features button from the Edit Attributes form 

    3. Select the desired 'Target Feature Layer' from the drop-down list.

    4. Uncheck fields that should not be copied over to the child (the default is to have all fields with matching names copy attributes from parent to child)

Selecting Coincident Geometries

Because copying facilitates the creation of coincident geometries, MobileMap has the ability to choose a specific feature when multiple are selected during query or edit operations.

    1. Use the edit tool to select the desired feature type (small pencil) 

2. Select the desired feature on the map 

    3. If the feature is coincident with another feature of the same type, MobileMap will notify the user of how many overlapping features were selected and display the attributes of all features in a window.  Pan to the right to see each feature’s attributes and select the desired one. 

Notes on Symbology

Features of different types that are likely to overlap should have symbology that makes it as easy as possible to distinguish them. To accomplish this, it is recommended that ‘base’ features (those that should appear below others) be given a higher line weight than other feature types. We typically use a line width of 3 or 4 for a base feature and then change the color and line width for other features that will be drawn on top of the base feature(s). Dashed lines can also be used for higher level features. Below is an example of symbology that could work well for multiple polygons in a feature service that will likely overlap on the map.

In this symbology it is assumed the Location Polygon is the feature that should be drawn below all other polygon types (with the exception of generic polygons).

• Observer ID
• Unique ID
• Setting configurable defaults
• Related Domains

Observer ID

MobileMap provides users with the option to automatically add their initials or name to all features that are collected.  While this functionality saves time and can help improve data quality, this field is only filled in when it is currently blank.  When a new feature is created, it will be populated when the data entry form is opened.  If an existing feature is edited in MobileMap and this field has not yet been filled in, it will be populated when the data entry form is opened.  If an existing feature is edited in MobileMap and this field has already been populated with a value, MobileMap will not overwrite the existing value.  MobileMap does not assume that if a user simply views or saves a feature that this field should be updated.

To utilize the Observer ID functionality, users need to set or verify two settings, ‘Observer Field’ and ‘Observer Initials or Name’.  To access these settings, hit the gear icon in the upper right, and scroll down to the ‘Data Model Settings’.   

• ‘Observer Field’ – this is the field that will be automatically populated in each feature class that contains it (upon feature creation). The default for this field is Observer.
• ‘Observer Initials or Name’ – this is what will be populated in the ‘Observer Field’.  This is typically filled in with a Surveyor name or initials.

Note that it is critical that the underlying data model contains the field that is entered in the 'Observer Field' setting, that it is of Text data type and that it is sufficiently long to support whatever users may insert as their 'Observer Initials or Name'.  Users should be instructed on what values to enter here, and some allowance should be made in the data model to account for slightly longer entries.  So, if users will use a 3-letter initial for this, we recommend using a text field with at least 5 characters.

Unique ID

If this field name is found and is Text data type, a unique ID will be generated when any of the listed components change. Example: 'fieldname:{field1}{yyyy}{observer}{000}' will generate a unique ID based on the field1 code plus the 4-digit year, plus the observer ID, plus 3-digit auto-incrementing number starting at 1, separated by a hyphen. The number will reset to 1 when any field changes. Component fields must be coded value domains.

Setting Configurable Defaults

MobileMap provides an interface for users to specify default values that they’d like to use for fields which will mostly have the same value across a site, day, or project area.  These values will automatically be applied to any new features that are collected, though the user will have the option of overriding these values before each individual feature is saved.

To Set Configurable Defaults:

Select the Main Menu, then select ‘Edit Configurable Defaults’.

This opens the configurable defaults menu.  This lists every field that uses a select list (rather than free text) by layer.  For any fields for which you’d like to use configurable defaults, simply select the value from the select list and verify that the ‘Enabled’ box is checked.  Select ‘Done’ and start collecting data with your configurable defaults. 

Calculated Fields

Calculated fields enable faster data collection by enabling automated the population of specified fields using equations that that are defined in MobileMap settings (Settings > Data Model > Calculated Fields).  One situation where calculated fields are useful is for generating unique IDs during data collection, where you want the ID to include meaningful information like the current date and time and the current user.  Another situation is where you want to run a calculation that would otherwise require the use of a calculator (e.g. Field X / 123) followed by manual data entry of the result.

The equations can include the following components:

1. Current date/time in one of the following formats: YYYY, MMDDYYYY, DDMMYYYY, YYYYMMDD, YYYYDDMM, YYYY-MM-DD, YYYY-DD-MM, YYYY-MM-DD-HH-MM-SS, YYYY-DD-MM-HH-MM-SS 
2. Universally Unique ID 'UUID'
3. Observer name or initials (stored in settings (above) 'Observer',
4. Field values - If an input field is included in an equation and that field utilizes a coded value domain (dropdown list), the calculated field can be recalculated when dropdown selection is changed
5. Mathmatical operators: +, -, *, /

There are 2 different formats for writing equations (Settings > Data Model > Calculated Feilds Equation Format).  Version 1 uses a comma separated list of calculated fields and associated calculations.  Version 2 (available in MobileMap 4.3.11 and later) uses a semicolon separated list and Arcade style syntax (e.g., $Feature.fieldname for field value).  Both formats support multiple calculated fields.

• V1 syntax: Target_Field:{Equation}{Components}:Overwrite_Flag
  • Equation components are all surrounded by curly brackets { }, no space between components
  • Overwrite flag is Y or N.  Y means overwrite the current value on 
  • Example: 'Field2:{YYYY}{Observer}{000}:N' (without quotes) 
    • Result if feature created in 2019 by user John Doe (Observer ID 'JD'): 2019JD001
    • Result on next feature (same year, same user):2019JD002
• V2 example:Target_Field:Equation + Components:Overwrite_Flag
  • Equation components are separated by spaces and operators
  • Components include functions in the format of FunctionName(parameters)
  • Overwrite flag is Y or N.  Y means overwrite the current value on 
  • Example: 'Field1:Date('YYYY') + Observer():N' (without quotes). 
    • Result if feature created in 2019 by user John Doe (Observer ID 'JD'): 2019JD

The table below includes the various equations components that are currently supported, along with examples using versions 1 and 2 of the equation format.  New equations should be written using version 2, unless unsupported functionality is required (e.g., auto-incrementing integers).  It is not possible to mix equation versions - a single version must be selected (Settings > Data Model > Calculated Feilds Equation Format).

MobileMap uses business rules to enforce business logic when creating and editing feature data.  Esri data models already support some business rules through the data type, domains and nullable status of a field.  MobileMap business rules extend the Esri data model by adding support for more complex business logic including validation rules and field relationships. 

• Validation Rules (Rules) utilize “if/then” logic (e.g., "if a tree has a broken top, a height measurement is required").  Rules implemented by creating records in a specific table named 'Rules' which is included in the feature service used by MobileMap when collecting data.  See the Data Model section below for a description of the fields in the Rules table.
• Field relationships (Related Domains) restrict choices in one attribute field based on the values selected in a related attribute field (e.g., if Plot Type is 'Variable Radius', Plot Size options should only include variable radius plot sizes and NOT fixed area plot sizes).  Related Domains are implemented by creating records in a specific table named 'Related_Domains' which is included in the feature service used by MobileMap when collecting data.  See the Data Model section below for a description of the fields in the Rules table.

Validation Rule Examples

Rules use a very flexible format to support a wide range of validation tests.  With this flexibility, however, comes complexity.  To help understand the general format of MobileMap rules, consider the following examples that can be supported via Rules:

1. The field 'DBH' cannot have a value greater than '40'
2. The field 'Net Acres' cannot have a value greater than the field 'Gross Acres'
3. If the field 'Tree Type' has a value equal to 'Overstory', then the field 'DBH' cannot have a value less than '5'
4. If the field 'Component' has the value 'Live', then the field 'Snag Class' cannot have a value that is not equal to Null
5. If the fields 'DBH' and 'Height' both have a value not equal to 'Null', then the field 'Tally Measure' cannot have a value equal to 'T'
6. The field 'DBH' cannot have a value greater than '20'; If it does, warn the user but don't prevent saving the feature

Validation Rule Structure

At the hightes level, Rules are broken into 3 main parts - the criteria, comparison and the test.  If the criteria is met, then the test is applied.  In examples 1 and 2 above, there are no criteria and the tests are always applied.  The comparison phrase in all of the examples above is 'cannot have a value'. If the test passes (is true), then the validation fails due to this comparison phrase. 

In example 3, the test is whether the value in the field 'Tree Type' is 'Overstory'.  If the criteria is met (because value of the 'Tree Type' field is set to 'Overstory'), then the test is applied, and the DBH is assessed to determine if it is less than 5.  If the test passes (because the DBH value is less than 5) then the comparison is applied.  Since the comparison is 'cannot have a value', then the validation rule fails.  This validation rule is an error (not a warning like in example 6), thus the user must fix this record before it can be saved.

The table below breaks down each of the six examples above into their component criteria, comparisons and the tests:

Managing Validation Rules

In order to assist with the mangement of Validation Rules, InventoryManager provides a dedicated interface for creating and editing validation rules.  The screenshot below shows this user interface in a typical InventoryManager implementation.  Even if your organization is not using InventoryManager to manage your MobileMap data collection, screenshot below is still helpful to explain the process and inputs for creating and editing validation rules via ArcMap, ArcGIS Online, or ArcGIS Pro.

Following the workflow of the user interface above, the process for creating a new validation rule is the following:

• If using InventoryManager:
  1. Select the layer that the rule should act upon
     • Click on the desried layer in the dropdown list.
  2. Define the criteria that must be met prior to applying the test.  In the example above, the test should only be applied if the field 'Contract_or_State' has a value equal to 'Contract'. If the field 'Contract_or_State' is null or has a value that is not equal to 'Contract', the test portion of the rule will not even be assessed.
     • If a criteria is needed:
       • Enter the criteria value
         • Enter the text or number in the input.  If the criteria value is null, enter as 'Null' (without quotes).  If the value is coming from a field, enter in the field within curly brackets { } (e.g., '{Contract_or_State}' without the quotes
       • Select the criteria operator
         • Click on the desried operator in the dropdown list.
       • Select the criteria field.
         • Click on the field name in the selection box.  If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names
     • If no criteria is needed because the test should always be applied (see examples 1, 2 and 6 above):
       • Uncheck the 'Include criteria' checkbox
  3. Select the test inputs
     • Select the test field.
       • Click on the field name in the selection box.  If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names
     • Select the test operator
       • Click on the desried operator in the dropdown list.
  4. Select the error type
     • Select 'Error' or 'Warning' from the dropdown list
  5. Enter the error (or warning) message to display to the user
     • Enter the full message that should be displayed to the user if the features does not pass the validation rule

• If using table capabilities of ArcMap, ArcGIS Pro, or ArcGIS Online. Example rule: If the field 'Tree Type' has a value equal to 'Overstory', then the field 'DBH' cannot have a value less than '5'
  1. Generate a table named Rules using either ArcMap, ArcGIS Pro, ArcGIS Online.  See the image below for the full data model of the Rules table. MB&G can provide a sample File Geodatabase with this data model upon request. Each row in the table defines one rule. "LEFT" inputs, aggregators, and operators correspond to the criteria portion of the rule.  "RIGHT" inputs, aggregators, and operators correspond to the test portion of the rule.  The "MAIN_OPERATOR" corresponds to the comparison portion of the rule.
  2. Define the criteria that must be met prior to applying the test by attributing the "LEFT" attributes of the Rules table.  In the example above, the test should only be applied if the field 'Tree Type' has a value equal to 'Overstory'. If the field 'Tree Type' is null or has a value that is not equal to 'Overstory', the test portion of the rule will not be assessed.
     • If a criteria is needed:
       • LEFT_INPUT1 - Enter field name within curly brackets { } (e.g., '{Tree_Type}' without the quotes. If more than one field is needed, separate the field names using comas (e.g., '{DBH},{Height}' without the quotes). 
       • LEFT_AGGREGATOR1 - Enter 'Value' in this field if one field is used as the LEFT_INPUT1 field.  Other options include 'Sum' to sum the values in multiple fields listed in the LEFT_INPUT1 field.
       • LEFT_OPERATOR - Enter the appropriate operator (=, !=, >,>=, <,<=)
       • LEFT_INPUT2 - Enter the text or number in the input.  If the criteria value is null, enter as 'Null' (without quotes).  If the value is coming from a field, enter in the field within curly brackets { } (e.g., '{Overstory}' without the quotes
       • LEFT_AGGREGATOR2 - Enter 'Value' if one field or a number or a text is used as the LEFT_INPUT2 field.
     • If no criteria is needed because the test should always be applied (see examples 1, 2 and 6 above):
       • LEFT_INPUT1 - Enter '1'
       • LEFT_AGGREGATOR1 - Enter 'Value'
       • LEFT_OPERATOR - Select '='
       • LEFT_INPUT2 - Enter '1'
       • LEFT_AGGREGATOR2 - Enter 'Value'
  3. Select the test inputs
     • RIGHT_INPUT1 - Enter the field name within curly brackets { } (e.g., '{DBH}' without the quotes). If more than one field is needed, separate the field names using comas (e.g., '{DBH},{Height}' without the quotes). 
     • RIGHT_AGGREGATOR1 - Enter 'Value' from the dropdown list for the field or 'Sum' if multiple fields are listed.
     • RIGHT_OPERATOR - Enter the appropriate operator (=, !=, >,>=, <,<=)
     • RIGHT_INPUT2 - Enter the text or number in the input.  If the criteria value is null, enter as 'Null' (without quotes).  If the value is coming from a field, enter in the field within curly brackets { } (e.g., '{DBH}' without the quotes
     • RIGHT_AGGREGATOR2 - Enter 'Value' from the dropdown list for the field or 'Sum' if multiple fields are listed.
  4. Select the Comparison
     • MAIN_OPERATOR - Enter '!='
  5. Select the error type
     • ERROR_TYPE - Enter 'Error' or 'Warning' from the dropdown list
  6. Enter the error (or warning) message to display to the user
     • ERROR_MESSAGE - Enter the full message that should be displayed to the user if the features does not pass the validation rule

Example rule: If the field 'Tree Type' has a value equal to 'Overstory', then the field 'DBH' cannot have a value less than '5'

Criteria

Test

Comparision and Error Type

Complete Rules Data Model

The full data model for the Rules table is shown in the image below.  MB&G can provide a sample File Geodatabase with this data model upon request.

Related Domains

Related domains define the relationship between two fields that each use coded value domains to provide a list of allowed values for that field.  Related domains restrict the choices in one attribute field based on the values selected in a related attribute field (e.g., if Plot Type is 'Variable Radius', Plot Size options should only include variable radius plot sizes and NOT fixed area plot sizes).  To achieve this, a set of related domains records are added to the Related_Domains table.  Each Related Domains record lists a value in the second field (target) dropdown list that should be available only if the specified value in the first field (source) dropdown list has been selected.  To do this, related domains utilize a source field, source value, target field and target value.  If the specified source value is selected for the source field, then the specified target value will be in the dropdown list for the target field.

Managing Related Domains

In order to assist with the mangement of Related Domains, InventoryManager provides a dedicated interface for creating and editing validation rules.  The screenshot below shows this user interface in a typical InventoryManager implementation.  Even if your organization is not using InventoryManager to manage your MobileMap data collection, the screenshot below is still helpful to explain the process and inputs for creating and editing Related Domains.   

Following the workflow of the user interface above, the process for creating a new Related Domains is the following:

• If using InventoryManager
  1. Select the layer that the rule should act upon (this will populate the list of available fields for the source and targe fields)
  2. Select the source field (this is the field that should then restrict the values of the target field dropdown list)
  3. Select the source value (this is the value of the source field that will restrict the values of the target field)
  4. Select the target field (this is the field that should be restricted based on the selected source field and value)
  5. Select the target value (this is a value that should be available to users in the dropdown list for the target field when the selected soure value is chosen for the selected source field).
  6. Click Add to create the new feature
  7. When editing a record, click the 'Edit' button to the right of that record in the list of related domains, then update the values as described above and finally click 'Update' and review the updated record in the list of related domains.

• If using table capabilities of ArcMap, ArcGIS Pro, or ArcGIS Online/Portal:
  1. Enter the source field name (this is the field that should then restrict the values of the target field dropdown list)
  2. Enter the code (NOT description) for the source value (this is the value of the source field that will restrict the values of the target field)
  3. Enter the target field (this is the field that should be restricted based on the selected source field and value)
  4. Enter the code (NOT description) for the target value (this is the value that should be available to users in the dropdown list for the target field when the selected soure value is chosen for the selected source field).

Note that while the InventoryManager Related Domains user interface includes a Layer, this is not actually stored in the Related_Domains table and is not required when enterying manually via ArcMap, ArcGIS Pro, or ArcGIS Online/Portal.  This means that once a Related_Domain record has been created and downloaded to MobileMap, it will be applied to ALL layers where both the source and targe fields exist, even if that layer is not the same as the layer that was defined in InventoryManager when creating the Related Domains record.

Related Domains Data Model

The full data model for the Related_Domains table is shown in the image below.  MB&G can provide a sample File Geodatabase with this data model upon request.

Disabling Validation Rules and Related Domains

MobileMap does not download data that have been deleted from the feature service.  This means that if a Validation Rule and Related Domain record are no longer valid, they cannot be simply deleted from the service.  In order for MobileMap devices to become aware that a Validation Rule and Related Domain record is not longer valid, it must be set to 'Archived' rather than actually deleted.  When MobileMap downloads updated data by pressing the Download button (Actions > Download), it will update that rule to a status of Archived, and will no longer apply the rule when validating features or applying related domains to subset related field dropdown lists.

GPS Collection of Points, Lines and Polygons

As described in 'Collecting Feature Data', your device's GPS (or external GPS) can be used to collection new spatial point, line and polygon features.  To collect new features via GPS, follow these steps

• Select the GPS data collection tool

• Select the layer you would like to collect features into
• Tap the screen anywhere on the map to collect vertices using the location determined by your GPS
  • For point features, a single tap will add a new point feature at your current location and will open the Attribute Editor to complete the data collection
  • For polyline and polygon features
    • The first tap (anywhere on the map) will add the first vertex of a new feature
    • Subsequent taps will add additional vertices to the current line or polygon feature
    • Double tapping the map will add the final vertex to complete the polyline or polygon feature and the Attribute Editor to complete the data collection

GPS Point Averaging, Elevation, and Analytics

To modify the number of GPS locations to average when collecting point features with GPS, select the desired number in the Number of GPS locations to average setting, under the GPS and Compass section of the general MobileMap settings (gear icon). The Maximum Wait Time to wait when collecting a point feature with GPS can also be modified under GPS and Compass section. These two settings do not affect collection of line or polygon features.

MobileMap allows users to store the number of points averaged to collect a point feature, the elevation recorded for a point feature, the GPS root mean squared error in attribute fields in point feature classes.  Attribute fields for corresponding GPS values are assigned under the Data Model section in MobileMap's general settings (gear icon). 

These settings are:

• GPS Elevation Field Name - If this field name is found in point feature layers, it will be used to store the elevation value (in the currently selected units) returned by the GPS, and will be the average elevation if GPS averaging is used.
• GPS Point Count Field Name - If this field name is found in the point feature layers and GPS point averaging is used, it will be used to store the number of points averaged.
• GPS Root Mean Squared Error Field Name - IF this field name is found in a point feature layer and GPS point averaging is used, it will be used to store the RMSE of points

GPS Editing of Point, Line and Polygon Geometry

Existing features can have their geometry updated using GPS.  This is most common with point features, but is possible with line and polygon features as well.  A typical scenario is the repositioning of an inventory plot with your current GPS location.  To edit the geometry of an existing feature using your device's GPS, follow these steps:

• Select the edit tool 

• Select the layer that contains the feature(s) you would like to edit
• Select the GPS tool from the top row of tools in the Attribute Editor form
• the GPS data collection tool

• Collect a new feature geometry using GPS by following the steps above for point, line or polygon
• If the feature is a polygon and the new and old geometries overlap, you will be asked if you want to replace, truncate, expand, split, etc. (see https://mobilemap.mbgapplications.com/edit-features for more details)

Tracks

MobileMap supports collecting track features via GPS.  Set the tracking feature layer in the Tracking Feature Layer setting, under the GPS and Compass section of MobileMap's general settings (gear icon). Best practice is to use a line feature layer for recording tracks. Polygons features are supported but may have issues recording if the MobileMap display shuts down due to inactivity.

To collect a track, select the track icon (  ).  The play, pause and stop buttons will be illuminated. Press play to start recording the track, Pause to pause recording (Play resumes and connects the first collected vertex to the last collected vertex), Stop to stop recording.  Once recording is stopped, the attribute form for the track feature will display.  Fill out required fields and save the feature.

Tracking Mode Spacing (meters): this setting, under the GPS and Compass section in MobileMap's general settings (gear icon), is the minimum distance between points that is needed to collect data in tracking mode. The value is in meters.

External Bluetooth GPS

To improve the spatial accuracy of data collected with MobileMap, it may be useful to use an external GPS receiver. There are a wide range of external GPS receivers that can be paired to your Android device to provide the GPS location information used by MobileMap. While the steps may vary with the particular GPS receiver and Android device, the general approach will typically be the same:

1. Download and install the Bluetooth GPS from the Google Play Store
2. Enable Mock GPS Provider in Android
3. Pair the Bluetooth GPS receiver with your Device

As an example of the more detailed procedure, the following steps can be used to pair a Garmin with the tablet, follow these steps:

1. Download and Install Bluetooth GPS from the Google Play Store (Bluetooth GPS is a third-party application and is not affiliated with Garmin or MB&G
2. Make sure the GLO is turned on
3. On your Android device, select "Settings" (gear icon on tablet’s home screen), then select "Bluetooth" and enable (slide slider to on)
4. Under available devices, locate the GLO and select “pair”
5. Once the GLO is paired, locate the Bluetooth GPS app on the tablet’s home display and launch the application
6. Check the box to "Enable Mock GPS Provider" within the app
7. From within the Bluetooth GPS app, press menu (location may vary), then select "Settings"
8. Under "Service Settings", select the "Reconnect" check box
9. Under "Connection Problems Related", select the check box for "Use Insecure Connection"
10. Press the "Back" button on your Android device
11. From the home screen of the Bluetooth GPS app, select the "Connect" button to the right of the Garmin GLO. If you see data filling up the fields below, then everything is working properly
12. To test further and ensure that GPS data is being received, select the "Status" and "Map" tabs at the top of the application.

• Status: Displays satellite information.
• Map: Displays your location on a map.

At this point, the Bluetooth GPS application can be closed and location information should be obtained by MobileMap.

(GEAR ICON ON MOBILEMAP HOME DISPLAY)

GENERAL 

Use landscape orientation
Uncheck to use portrait orientation. Must restart app for this change to take effect. 

Autoload previous map cache
Check box to auto-load the last used map cache

Keep Device Awake
Prevent device from going to sleep when MobileMap is running

Show Data Loading Progress and Results
Show data loading Progress and results on startup and map cache switch - helpful to confirm data loaded properly 

Show Point Geometry Editing Instructions
Check to display instructions when editing point geometries 

Show Line Geometry Editing Instructions
Check to display instructions when editing line geometries 

Show Polygon Geometry Editing Instructions
Check to display instructions when editing polygon geometries

Stylus Only Mode
Check to only accept user input from stylus. Device must have digitizer and active stylus (e.g., S-Pen)

Use Field Aliases
Check box to display field aliases, rather than field names, in attribute editor 

Enable Cloning of Features
Check box to enable cloning of features from one layer to another by copying geometry and (optionally) attributes with matching field names in each layer

Font Size
Select default font size for settings and editing attributes 

DATA COLLECTION AND EDITING 

Digitizing Method
Select desired method for digitizing lines and polygons 

Minimum polygon vertex spacing
Minimum spacing (m) between vertices when digitizing in 'trace' mode 

Minimum Mapping Unit - Trace Mode
Enter in the minimum allowed area (square meters) for polygons when using trace mode (default is 100 square meters, ~1/4 acre) 

MEASUREMENT AND NAVIGATION 

Linear Measurement Unit
Select desired unit for measuring lengths 

Area Measurement Unit
Select desired unit for measuring areas  

Projection / Units for Coordinates
Select desired projection and units for displaying GPS coordinates 

Display Compass
Check to display a digital compass (compass only works on devices with magnetometers)

Magnetic Declination
Enter magnetic declination for proper compass functionality  

Enable Proximity Alert
Check to enable alert sound when arriving at a feature (also set distance below) 

Proximity Alert Distance
Enter distance (using linear measurement units) at which an alert should sound when navigating to a feature  

AUTHENTICATION SETTINGS 

ArcGIS Username
ArcGIS Online/Server Username 

ArcGIS Password
ArcGIS Online/Server Password 

Email Address
Email address - used when registering device with MBG  

SYNCHRONIZARION SETTINGS 

Author Field Name
Must be same field for all layers in service, used for synchronization 

Created Date Field Name
Must be same field for all layers in service, used for synchronization 

Editor Field Name
Must be same field for all layers in service, used for synchronization

Last Edited Date Field Name
Must be same field for all layers in service, used for synchronization  

PHOTO SETTINGS 

Photo Fields
Comma separated list of text fields that will be used to collect photos during data collection (e.g., 'Photos_Before,Photos_After')  

Include Field Name in Photo Filenames
Check box to append the photo field name to the end of the photo filename - otherwise filename will be month_day_year_hour_minute_second for new photos, and month_day_year_originalfilename for existing photos) 

Enable Selection of Existing Photos
Check box to enable selection of existing photos as an alternative to taking a new photo during photo collection 

Output Photo Size
Select output photo size. All photos captured will be resized to this setting to control disk usage and upload speeds 

DATA MODEL SETTINGS 

Observer Field
Name of the field that stores observer (surveyor, cruiser, crew, etc.) name or initials 

Observer Initials or Name
Enter observer (surveyor, cruiser, crew, etc.) name or initials. May need to verify field length if using full name.  

Length Field Name
If this field name is found for Lines or Polygons, length will be calculated in current units  

Area Field Name
If this field name is found for Polygons, area will be calculated in current units  

Custom Created Date Field Name
Comma separated list of field names. If any of these fields are found they will be populated with current date and time when feature is created. This field will not be overwritten by sync  

Custom Edit Date Field Name
Comma separated list of field names. If any of these fields are found they will be updated with current date and time whenever an existing feature is re-saved. This field will not be overwritten by sync  

GPS Elevation Field Name
If this field name is found in point feature layers, it will be used to store the elevation value (in the currently selected units) returned by the GPS, and will be the average if GPS averaging is used 

GPS Point Count Field Name
If this field name is found in point feature layers and GPS point averaging used, it will be used to store the number of points averaged  

GPS Root Mean Squared Error Field Name
If this field name is found in point feature layers and GPS point averaging used, it will be used to store the RMSE of points averaged, in the currently selected units  

Field Name and Format for a Unique ID
If this field name is found and is Text data type, a unique ID will be generated when any of the listed components change. Example: 'fieldname:{field1}{yyyy}{observer}{000}' will generate a unique ID based on the field1 code plus the 4-digit year, plus the observer ID, plus 3-digit auto-incrementing number starting at 1, separated by a hyphen. The number will reset to 1 when any field changes. Component fields must be coded value domains.  

Related Domains Table
Name of the Related Domains table (if present) which allows subsetting values of one Domain by the selected value of another Domain  

Rules Table
Name of the Rules Table (if present) in the feature service 

Read Only Fields
Comma separated list of fields that should be read only in the attribute editor (e.g., 'Field1,Field2')  

Hidden Fields
Comma separated list of fields that should be hidden (not displayed) in the attribute editor (e.g., 'Field1,Field2')  

DATA FILES (CSV) 

X Coordinate Field
Field name for X coordinates 

Y Coordinate Field
Field name for Y coordinates 

GPS AND COMPASS 

Display GPS Accuracy
Check box to display the estimated GPS horizontal accuracy (in currently selected units) along with GPS coordinates and elevation

Tracking Mode Spacing (meters)
Enter minimum distance between points when collecting data in Tracking Mode. 

Update Frequency for Tracking Path
Lower value updates tracking path more often (1 = updates every time new GPS location received) 

Tracking Feature Layer
Case sensitive name of tracking feature (must be polyline geometry) 

Number of GPS locations to average
Select number of GPS locations to average when collecting point features with GPS. Does not affect collection of line or polygon features. 

Maximum Wait Time
Select maximum time (seconds) to wait when collecting point features with GPS. 

SEARCH 

Search Buffer
Select search buffer distance (m) for selecting existing features 

ZOOM LEVELS 

Minimum Zoom Level
Select the minimum zoom level (L1 is default )

Maximum Zoom Level
Select the maximum zoom level (L20 is default) 

Map Scale for Labels
Select the map scale at which labels should appear (when selected for a layer in display properties)  

Display scale and resolution
Check box to Display map scale and resolution in lower left of map

MobileMap CRUISE 

Enable Cruise Functionality
Check box to support collection of cruise stand, plot, tree and log data (requires layers, tables and settings below)  

Check Cruise Mode
Check box to enable Check Cruise Mode  

Cruise Type Field
Name of the field that stores Cruse Type ('S' for Standard, 'C' for Check Cruise)  

Stands Feature Layer
Name of the Stands Feature Layer in the feature service  

Stand ID Field
Name of the stand ID field 

Plots Feature Layer
Name of the Plots Feature Layer in the feature service 

Plot ID Field
Name of the plot ID field  

Trees Table
Name of the Trees Table (no geometry) in the feature service 

Maximum Number of Tree Rows
Select the maximum number of tree rows to display at any one time (fewer rows improves performance) 

Database Backup Interval
Select the frequency at which the entire database should be automatically backed up 

Trees Height Field
Name of the Trees Height Field  

Trees Diameter Field
Name of the Trees Diameter Field  

Trees Species Field
Name of the Trees Species Field  

Tree ID Field
Name of the tree ID field 

Tree Fields to Ignore
Comma separated list of fields that should be hidden in tree editor (e.g., volume)  

Fields to Inherit From Stand and/or Plot
Comma separated list of fields that should be inherited from Stand to Plot and/or from Plot to Tree. If field name is present in both layers (e.g., stand and plot) the value will be copied from parent when value is blank/null in child (useful for filtering trees).These fields will be hidden in the tree table  

Logs Table
Name of the Logs Table (no geometry) in the feature service  

Log ID Field
Name of the log ID field  

Log Length Field Name
Name of the log length field 

Unique ID Field Name
Name of the field that will store the Unique ID (formerly called GUID; must be present in Stands, Plots, Trees and Logs tables) 

Parent ID Field Name
Name of the field that will store the ID to parent stand, plot or tree (formerly called Parent_GUID; must be present in Plots, Trees and Logs tables)  

Notes Field Name
Name of an optional field in Trees and/or Logs tables that are used for notes (field will appear wider in form to show more information)  

Check Cruise Score Field Name
Name of an optional field in Plots feature class that is used to store a calculated check cruise score (should be integer type)  

Check Cruise Scoring Rules Name
Name of the check cruise scoring rules to be used  

LICENSE INFORMATION 

Android ID
Copy Android ID and provide to MB&G when requesting a license key 

License Key
Paste in the license key from MB&G here

Photo Upload directly from MobileMap – If you set a Spatial CMS photo upload URL in settings, you can use the new ‘Upload Photos’ menu item to upload photos from MobileMap.  Select the photos you want to upload then tap ‘UPLOAD’.  You will see a progress bar advance and each filename will turn green when done.  If uploading just some of the photos, tap the refresh tool when done to see the list updated to show only those photos which photos have not been uploaded. 

There are a wide range of data collection workflows and data models for timber inventory (cruise) data collection. The most common workflow has the following steps:

The plot layout tool can be used to create a grid of new plots within a cruise stand.  Keep in mind that this tool will create multiple features automatically.  If there are required (non-nullable) fields, these values will need to be set on each plot before it can be successfully uploaded.  One way to do this is to use default values in the data model.  Another way is to use Configurable Defaults in MobileMap.  Defaults can be combined with Configurable Defaults to provide a global default (in the data model) and a local default (for a specific user on their MobileMap device).  In both cases, if defaults are found, the plot layout tool will apply them when creating new plots. 

To use the plot layout tool, follow these steps:

Configure the tool in settings:

MobileMap Cruise > Enable Cruise Functionality - Check this box to enable cruise functionality, which is required for plot layout

MobileMap Cruise > Enable Creation of New Plots - Check this box to enable enable creation of new plots.  This is required for manal plot creation and use of the Plot Layout tool

Plot Layout > Enable Plot Layout - Check this box to enable plot layout

Plot Layout > Stand Boundary Buffer - if a value greater than 0 is used here, the stand boundary will be buffered inward by the selected number of feet.  This will prevent plots from being created along the stand boundary.

Plot Layout > Minimum Plot Count - Minimum number of plots per stand when using plot layout tool

Plot Layout > Maximum Plot Count - Maximum number of plots per stand when using plot layout tool

Plot Layout > Target Plot Density - Target plot density (area per plot, in currently selected area units) when using plot layout tool.  To achieve a density of 1 plot for every 2 acres, enter a value of 2 in this field.

Plot Layout > Plot Density Field - Optional field name to read plot density value from, on a per stand basis, when using plot layout tool.  Can be useful when different strata have different target densities

Plot Layout > Plot X:Y Ratio - Ratio of spacing in X to Y, in format of (X spacing):(Y spacing).  Default is 1:1.  To simulate pattern of 4 chain by 5 chain grid, use "4:5" (without quotes).

Plot Layout > Plot Starting ID - The plot ID, or plot number that will be used for the first plot.  Examples are '1' or '123' (no quotes).  You should only have to set this the first time you run the tool, internally the number will be auto-incremented each time a new plot is created with the Plot Layout tool.  If you want to re-set the auto-increment value, set this field to the desired next plot.  

Plot Layout > Use Diamond Layout - Check box to use a diamond layout pattern instead of square or rectangle

Data Model > Area Field - set this to the field in the stand feature layer that stores the area of the stand.  This might be 'Area', 'Acres', 'Cruise_Acres', 'Net_Acres' or something different.  MobileMap uses this field to calculate the number of plots to create

Lay Out Plots

Select a stand for plot creation – Once the settings have been configured, begin plot creation by using the edit tool on the Stand layer and selecting an existing stand. Then select the plot layout icon (9 points, upper right of toolbar). 

Review the area, minimum and maximum plots, plot density and target plot count information.  The target plot indicates the number of plots that the tool will create.  If this number does not seem right, edit it within the window by pressing the back cursor and type in the number of plots you prefer. Below is an example which shows it originaly had 47 plots but changed to 10 plots   Press ‘CREATE PLOTS’.  The tool will generate plots and report the number of plots created and the number of iterations that were needed to create the plots. 

Select 'DONE' to return to the Stand attribute editor.  Tap the Save icon to close the stand and begin collecting plot level data.

The number of plots now can be viewed within the stand alond with PLOT_ID number indicated next to them as labels. This can be set in the layers menu drop down for plots.

When MobileMap Cruise functionality is enabled in settings and a cruiser is editing a plot feature, a tree icon will be displayed in the upper right of the attribute editor. To record trees, tap the tree icon to open the tree table, which acts as a digital tally card.

Tree List Design

The tree list has been designed like a tally card, and displays like an Excel spreadsheet.  Each row in the list represents a single tree, and each column represents an attribute field from the data model.  Enter data into appropriate cells using the software keyboard, the tree list does not use dropdowns or other controls.  Below are some details about data entry fields in the tree list:

• Data can be entered one row at a time, entering all values for a tree before moving to the next tree.  Or, data can be entered one column at a time.  For example, some cruisers choose to 'spin' a plot, and record all 'in' trees by entering in just the species information for each tree.  After all trees have just their species recorded, the cruiser then goes to each tree and records additional information such as DBH, height, etc.
• As with all data collection interfaces in MobileMap, the list of available attribute fields is dictated by the feature layer in the data model. 
• Some fields in the data model may be hidden from the tree list.  Hidden fields are defined in the MobileMap settings, and are typically loaded from the feature service when importing settings.
• Some fields may have default values which are populated either by the default values in the data model or through inheritance from their parent plot
• Some fields may be required (asterisks in column name).  Typically the species field is required, and it is common to require DBH and hieght fields. 
• Some fields may have a limited set of discrete allowed values (e.g., fields that use a Coded Value Domain).  The species field commonly uses a pre-defined list of species 2-letter codes.  To see the list of allowed values tap on any cell in that field (column) to select it, then tap the question mark “?” button to see the list of allowed values.
• Some fields may support continuous values, but may be limited to values within a specified range (e.g., fields that use a Range Domain). The DBH field commonlly uses a range domain to ensure that values are greater than 0 (or some other number) and below the maximum anticipated tree diameter for all trees.  If a value entered is outside of the defined range, an error message will be displayed when the tree records are saved
• Some fields may have business rules applied to them using the 'Rules' table in the MobileMap data model.  Business rules support complex rules (more complex than Coded Value Domains and Range Domains) such as if/then statements.  One common business rule is "if a tree is a site index tree, then a tree height measurement is required"
• The column labels displayed in the tree list come from the alias assigned to the attribute field in the Esri data model for the Trees table.  If a long alias is used, it may be truncated or wrap in the column header.  We recommend that tree field aliases be limited to between 2 and 4 characters, with shorter aliases used when a greater number of attribute fields will be displayed in the Tree List.  Common abreviations include Sp for Species, DBH for diamater, Ht for Height, etc.  Note that required fields will include an asterisk appended to the alias, which will increase the number of characters displayed in the column header. 

• The default layout of the tree list is to display all editable fields using the same column width.  If customization of field widths is required (e.g., to accomodate additional digits for DBH when there are a large number of displayed fields), the tree table field widths can be modified in MobileMap Settings (Settings > MobileMap Cruise > Trees > Tree and Log Field Column Width Weights). 

  • The default weight is 1 for all columns.  Using larger or smaller values increases or decreases the column width, respectively, for a particular column.
  • The weights are proportional, so a weight of 1.5 will draw that column with 150% of the width of the other fields. 
  • If a column needs to be wider (e.g., to support a value like 12.3 for DBH) then a larger weight can be assigned to that column.
  • If a column should be smaller to free up space for other fields, use a value less than 1 (e.g., 0.5). 
  • To enter in appropriate weights, use a comma separated list of fields and their associated column width weights.  The format for this setting is 'fieldname:weight,fieldname:weight' (e.g., 'DBH:2,Height:1.5' - without quotes). 
  • Given the complexity of the field weight syntax, when this setting is needed it is typically loaded from the feature service when importing settings.

ROW AND CELL HIGHLIGHTING

• The currently selected tree row will be shown in yellow. When inserting or deleting tree rows, it is important to note which tree row is selected (in yellow). 
• The currently selected cell will be shown in light blue (cyan). Individual cells that are highlighted red indicate cells with validation errors which must be fixed prior to saving that tree and closing the tree table. If a user attempts to save or close the table when validation errors are present, they will see a popup message describing the errors as shown below.

NUMBER OF TREES TO DISPLAY

Under some inventory scenarios, a large number of trees may be recorded on a single plot (e.g., a single 'plot' used to record a 100% tally on a stand).  When too many trees are displayed at once, it can affect the performance of the tree list.  To ensure maximum performance when collecting a large number of trees per plot, the Tree List can be set to only show a maximum number of trees (Settings > MobileMap Cruise > Trees > Maximum Number of Tree Rows).  The default value for this setting is 20, but it can be set between 4 and unlimited.

INSERTING AND DELETING TREES

• Inserting a tree row (+ icon) will insert an empty tree record ABOVE the currently selected tree row. 
• Deleting a tree row (trash can icon) will delete the currently selected (in yellow) row.  You will be asked to confirm any tree delete operations.

LIMITING DISTANCE CALCULATION

If your data model supports calculation of limiting distance, the ruler icon can be used to calculate the limiting distance to any tree.  In order to use the limiting distance, the following are required:

• The plot feature layer must have a field for basal area factor and the field name must be set in settings (MobileMap Cruise > Stands > Basal Area Factor (BAF) Field)
• The BAF field must store BAF data in the correct format, using a three-letter prefix for BAF or FIX (for fixed area plots) followed by the BAF value (e.g., BAF10 for BAF of 10) or the portion of an acre (e.g., FIX50 for 1/50th acre fixed area).  This field should use a coded value domain to avoid typos.  Typically this field is applied at the Stand and Plot level and used with field inheritance to allow a user to set at the Stand level, inherit to all plots, then use in the tree list.
• Support for Limiting Distance calculation must be enabled in MobileMap Settings (MobileMap Cruise > Trees > Enable Display of Limiting Distance)
• A tree record must be selected (yellow highlight)
• The DBH field for the selected tree must already be entered
• Limiting distance calculation can be set to report distances to either the center of the tree (default) or the face of the tree by adjusting the setttings (MobileMap Cruise > Trees > Calculate Limiting Distance to Face of Tree)

LOG DATA COLECTION

If log data is supported, select the edit button (pencil icon) in the 'Logs' column to open the Logs List (similar to the trees list).  Logs are entered in the same way as trees, but must be entered sequentially from the first (butt) log up.  Logs are commonly used only for recording defect.  For this to work correctly, all logs below the highest log with defect must be entered.  For example, if the third log up the tree has 20% defect, logs 1 and 2 must be entered, along with their length and defect, even if they have no defect (defect = 0).

CHECK CRUISE

MobileMap supports check cruising by using the Tree List in a special Check Cruise mode.  When check cruising, the check cruiser updates the existing stand and plot features (to add details, change status, etc.) and collects duplicate tree records (one check cruise tree for every standard tree).  See the next chapter for more information on check cruising.

SAVING YOUR DATA AND CLOSING THE TREE LIST

To save the tree data in the tree list, select the save button (disc icon).  Saving triggers a validation process which checks all tree rows for a range of validation rules including allowed values (coded value domains), allowed data ranges (range domains), required (non-nullable) fields and business rules (e.g., if/then rules).  If any errors are found, a popup will display the errors by indicating which tree(s) and field(s) contain errors.  Only the first 5 errors will be displayed in the error popup.  Select OK to close the error window, fix the data errors, then select save to re-validate your data.  If there are no validation errors, a small temporary popup will be displayed at the bottom of the screen indicating that all tree records were successfully saved.

To save the tree data and close the tree list at the same time, select the back button (left arrow icon).  This will trigger the save process described above, but if there are no validation errors it will immediately close the tree list and return to the parent plot after it finishes saving the tree data.

AUTO-SAVE OF TREE DATA

MobileMap supports auto-saving of data at specified data intervals.  The default behavior is to auto-save all new and modified data every time a plot record is saved.  This behavior can be changed in settings (MobileMap Cruise > General > Database Backup Interval) to increase (or decrease) the frequency of auto-saving.  One scenario is when a large number of trees will be collected on a set of plots (e.g., a 100% tally on a psuedo-plot).  For example, auto-save frequency can be set to backup every 5, 10, or 20 trees to prevent data loss if a device fails while in the middle of collecting a plot.  Data backups will, however, require a pause in data collection and thus should be used carefully to ensure they don't impact data entry efficiency.  

DOUBLE SAMPLING (SUBSAMPLING)

Double sampling, also called subsampling, is a cruising methodology in which only some of the visited trees are measured.  When we use the term 'sampling', we refer to the use of Plots (or sample points) for assessing a subset of trees on a stand.  Sample plots can be fixed area or variable radius plots, and are in contrast to 100% tally cruises in which all trees are assessed at the stand level without the use of plots.  Double sampling takes this approach a step further by measuring only some trees that are visited (or assessed), and simply counting the others.  The goal of double sampling is to reduce the effort (time, cost) of cruising by reducing the number of field measurements that must be taken.  Double Sampling is typically combined with plot-based sampling but can also be used with 100% tally cruises (see Sample Tree Ratios below).  MobileMap currently supports 4 different methods of double sampling: Point Count Measure, First Tree North, Big BAF, Sample Tree Ratios. 

A key concept in double sampling is the definition of 'sample groups'.  Sample groups are typically defined by species, or by a combination of species and products.  They may also be defined by broader tree groups, like harwoods vs softwoods.  Measurements for 'measure' trees typically include, at a minimum, the species and DBH of that tree, along with enough information to calculate tree volume using the selected volume calculations for the cruise.  Even for measure trees, it is common for height information to be collected only on a subset of trees, and interpolated, or 'dubbed', using known or calculated diameter to height ratios for the remaining trees.  Tally trees, by contrast, do not have any measurements and the only information that is recorded is what is required to determine their sampling group (e.g., species and product) as well as their quantity (count). 

Below is a brief description of the double sampling approaches supported within MobileMap:

• Point Count Measure (PCM) - Point Count Measure is perhaps the simplest method and uses two different plot types within each stand: measure plots and count plots.  On measure plots, all trees are measured with sufficient information to calculate tree volume using the selected volume calculations. PCM can be used with fixed area and variable radius plots, but not 100% tally cruises.
• First Tree North (FTN) - First Tree North uses a single plot type.  When using FTN, the first tree of each sample group is measured on each plot.  The 'first' tree is determined by doing a sweep starting facing due North, then rotating clockwise around the plot.  The first tree encountered in each sample group is measured.  All other trees are tallied.  FTN can be used with fixed area and variable radius plots, but not 100% tally cruises.
• Big BAF - Big BAF uses a single plot type (like FTN) but two different BAFs.  The main BAF is used to determine which trees are 'in' on the plot.  The big BAF (often 2 times the BAF of the main BAF) is used to determine which trees on the plot should be measured.  Those trees that are 'in' via the main BAF but not 'in' via the Big BAF are tallied.  Big BAF has some advantages over First Tree North in that the selection of measure trees is not random within a plot.  Big BAF will tend to select the larger trees while this may be biased, it may better represent the higher value trees that the cruiser hopes to characterize with more certainty.  Big BAF is only relevant for variable radius plots (not fixed area plots or 100% tally cruises).  More information on Big BAF can be found here https://academic.oup.com/forestry/article/90/5/649/3749606
• Sample Tree Ratios (STR)  - Sample Tree Ratios use predefined ratios to select which trees should be measured.  Sample Tree Ratios are established for each sample group and applied across the stand (rather than at the plot level like in FTN or Big BAF).  An example ratio is 'DF:S:5' which indicates that Douglas fir sawtimber should be sampled at a ratio of 1:5, meaning that one tree should be measured out of every 5 assessed (the other 4would be tallied).  MobileMap will always flag the first tree in a sample group as a measure tree, then will use a random component when flagging additional trees.  In the previous example, it would flag tree 1 as measure, then 1 tree between trees 2 and 6, 1 tree between trees 7 and 11, etc. STR can be used with fixed area plots, variable radius plots and 100% tally cruises.

Data Model

In order to support sampling, several fields must be included in the cruise data model

• Sample_Type - This field should be a text field in both the Plot and Stand feature layers that uses a Coded Value Domain that lists all double sampling methods that are supported, and an option for 'None'.  The list of accepted values are: 
  • BB = Big BAF
  • STR = Sample Tree Ratio
  • FTN = First Tree North,
  • PCM = Point Count or Measure
  • None = no sampling
• Big_BAF - If the Big BAF method is supported, this field should be a text field that uses a Coded Value Domain that lists all of the BAF values that are appropriate for Big BAF.  Allowed values should follow the same convention
• PCM_Ratio - If Point Count Measure method is supported, this field should be a text field that uses a Coded Value Domain that lists all of the allowed ratios in the format of '1:2', '1:3', '1:4', etc.
• STR_Ratios - if Sample Tree Ratios are supported, this field should be a text field that will store a comma separated list of ratios (e.g., 'DF:S:5,DF:P:10,GF:XX:2,XX:XX:3')
• Tally_Measure - This field should be a text field in the Tree feature table that uses a Coded Value Domain with the values 'M' for measure and 'T' for tally.  MobileMap will update this field automatically when it can determine if a tree should be measured or tallied.  Automatical determiniation of T or M will be possible for PCM, FTN and STR, but not for Big BAF

Settings

In addtion to these fields, there are a number of settings in MobileMap that need to be configured depending upon which Doubl Sampling methods are supported

• Settings > Tree Sampling> General
  • Use Tree Sampling - Check box to indicate that tree sampling may be used to determine if a tree should be measured rather than tallied.  When enabled, MobileMap will alert cruiser when recording the nth tree so cruiser knows to measure DBH, height, etc.  Complete settings below to define the sampling type field and values representing the different supported sampling types
  • Stand-Level Sample Type Field - Name of field in the Stands table that stores the type of sampling (if any) should be used for a given plot.  Default field name is 'Sample_Type'. MobileMap expects that this field will use a coded value domain with the following values for supporting sampling types: BB = Big BAF, STR = Sample Tree Ratio, FTN = First Tree North, PCM = Point Count or Measure, None = no sampling.
  • Plot-Level Sample Type Field - Name of field in the Plots table that stores the type of sampling (if any) should be used for a given plot.  For 'Point Count Measure' approach, sample type at the Stand level will be used to set plots to Count or Measure.  Default field name is 'Sample_Type'. MobileMap expects that this field will use a coded value domain with the following values for supporting sampling types: BB = Big BAF, STR = Sample Tree Ratio, FTN = First Tree North, PCMC = PCM Count, PCMM = PCM Measure, Tally = all trees tallied (same as PCMC, all trees counted and not measured) None = no sampling (same as PCMM, all trees measured).
  • Tree-Level Sample Type Field Name and Values - Name of field in the Trees table (field name should be different than plot-level sample type field) that stores whether tree is a Measure tree or a Tally tree, and the values representing 'measure' and 'tally'. Use colons to separate 3 components.  Typically the values will come from a coded value domain assigned to this field.  Default field name is 'Sample' and values are 'M' and 'T' (e.g., 'Sample_Type:M:T',without quotes).  Note, cannot use non-nullable fields for fields like DHB or Height, since tally trees do not require these measurements (Species and Tally or Count can be non-nullable).
• Settings > Tree Sampling> Sample Group Methods - FTN, STR
  • Tree Sample Group Attribute Fields - Comma separated list of fields in the tree table that define a sample group for First Tree North (FTN) and sample tree ratio (STR) subsampling.  Default value is 'Species,Product' (without quotes).
  • Sample Tree Ratios Field - Field in the Stand and/or Plot table that stores the sample tree ratios.  Default value is 'Sample_Tree_Ratios' (without quotes).
  • Default Sample Tree Ratios - Comma separated list of sample tree ratio entries.  For each sample tree ratio, enter the grouping fields and the ratio, separated by colons.  For default, use 'XX' for text or '0' for integer fields. E.g., 'DF:S:5,DF:P:10,GF:XX:2,XX:XX:3' (without quotes) indicates that every 5th Douglas fir sawtimber tree, every 10th Doug fir Pulp tree, every second Grand fir (any product), and every third tree for all other species and products should be measured and the rest of the trees should be tallied by species or species + product (according to the Sample Tree Ratio Fields above).  Each sample tree ratio included here will be included when populating a new sample tree ratio entry using the sample tree ratio editing tool.  Once created, they can be modified or augmented within that tool
• Settings > Tree Sampling> Big BAF
  • Tree-Level BAF Field for Big BAF method - Name of field in the Trees table that stores the type of BAF that includes a given tree.  Default field name is 'BAF_Type'. MobileMap expects that this field will use a coded value domain with the following values BAF types: B = Big BAF, S = Small BAF.

Overview

Check cruising is a special case of timber cruising, where an auditor or 'check cruiser' revisits a plot and remeasures all data for quality control purposes.  MobileMap supports check cruising by providing support for denoting if a tree measurment is a standard or check cruise measurment, and by providing a tailored tree list when conducting check cruises.

Prerequisites - Data Model

In order to use MobileMap for check cruising, your data model must include a field named 'Cruise_Type' in the Trees table (and Logs table if logs are being recorded).  This field should be a String data type and should use a Coded Value Domain with only two values, 'S' for standard and and 'C' for check cruise.  It is also common to include some extra fields to the Stands and Plots feature classes to store data that will be entered by the check cruisers.  Examples might include: 'Check_Notes', 'Check_Habitat', 'Check_Flagged_OK'.  The extra fields can be hidden from cruisers by adding them to the hidden fields list (Settings > Data Model Settings > Hidden Fields).

Enabling Check Cruise

To enable check cruising go to Settings > MobileMap Cruise > Check Cruise, then check 'Check Cruise Mode'. When Check Cruise Mode is enabled, MobileMap will record a C (check cruise) in the Cruise_Type field for each tree, and it will also display a read-only tree list at the top of the editable tree list.  When Check Cruise Mode is not enabled, it will record an S (standard cruise) in the Cruise_Type field for each tree, and won't have the read-only list at the top of the screen.

Optionally, you can also  check 'Enable Copying of Cruise Trees into Check Cruise' which can speed up check cruise data entry.

Conducting A Check Cruise

To conduct a check cruise, first complete the standard cruise with Check Cruise Mode disabled, upload all data, and complete any data quality checks.  Next, have check cruisers download the relevant data, using download filters (Actions > Edit Download Parameters) where appropriate.  Enable check cruise mode, then use the standard cruising workflow to navigate to a plot that will be checked and open the tree list (e.g., select Edit tool, tap on desired plot, then tap on Tree list).  You will see a tree list that is divided into two main sections.  The top section is a read only tree list showing the original cruise data.  The bottom list is an editable tree list for the check cruise tree measurments.  If 'Enable Copying of Cruise Trees into Check Cruise' was checked in settings, the check cruiser can tap the copy icon before any trees have been recorded to copy the cruise tree list to the check cruise tree list.  Trees can be created and edited using the standard cruising approach.  Whenever a check cruise tree row is selected in the check cruise tree list, the corresponding tree in the read-only cruise tree list at the top of the display will be highlighted.

Special Considerations

In order to maintain the relationship between a cruise tree and a check cruise tree, MobileMap (and InventoryManager) use the Tree ID.  Thus, the order of trees in the check cruise tree list is important, and must match the order of the trees in the read-only cruise tree list at the top of the display.  There are two special cases which need to be handled - new and missing trees:

• If a cruiser recorded a tree as 'in', but the check cruiser has determined that the tree is 'out', the tree should be entered in the check cruise tree list in the same order that it appears in the cruise tree list, but the tally or count field should be set to 0 to indicate that this tree should not be included in compilation.  It is common for the check cruiser to also note this in the note or comment field. 
• If a tree was omitted by a the cruiser, but the check cruiser has determined that the tree is 'in', it should be added to the bottom of the tree list, after all matching tree records have been entered.  Similarly, a comment should be entered by the check cruiser.

Overivew

MobileMap supports offline reporting of stand summary statistics.  These statistics can be useful for evaluating stand attributes while in the field.  They include a range of statistics calculated from the plot and tree data collected for a single stand.  Stand summary statistics do not currently include log-level information.  The following metrics are included in a stand summary report.

• Stand Acres
• Plot size
• Number of plots
• Number of measured plots
• Total number of 'in' trees
• Number of tallied trees
• Number of measured trees
• Ratio of measured trees to total
• Measured trees by species (total trees, ratio)
• Trees per plot average
• Trees per plot standard error (%)
• Trees per plot min (95% CI)
• Trees per plot max (95% CI)
• Basal Area average
• Basal Area standard error (%)
• Basal Area min (95% CI)
• Basal Area max (95% CI)
• Basal Area by species 
• TPA average
• TPA by species
• QMD average
• QMD by species
• Volume average (per acre)*
• Total volume*
• Volume standard error (%)*
• Volume min (per acre, 95% CI)*
• Volume max (per acre, 95% CI)*
• Volume (per acre) by species*

* Required an specifically formated tree volume database.  More details on generating this database can be provided upon request

Generate Stand Summary

Steps to generate a stand summary for a stand after measuring plots

• Select edit tool

• Select stand layer

• Tap on desired stand to open
• Select the Plots Tool

• Select 'Stand Summary'

• You will see a message telling you that MobileMap is calculating the stand summary.  Stand summaries can take several minutes to complete if there are a large number of plots and trees.

• Once the stand summary is complete, it will open in an new screen.  The screen is split in 2 sections, each one can be scrolled up and down.  The top contains stand level summary statistics, while the bottom contains details on each measured plot.

• To save the stand summary, tap 'Save'.  MobileMap will save the stand summary information (top section of screen shown above) to a text file stored in the Downloads folder of your internal storage.  You can use a text viewer on your device to open and read this report, or send it via mail, copy to a PC, etc.

Configuration

In order to successfully configure MobileMap to support Stand Summaries, the following settings must be properly set:

Settings > MobileMap Cruise > General

• Use Tree Sampling
  • Check box to indicate that tree sampling may be used to determine if a tree should be measured rather than tallied.  When enabled, MobileMap will alert cruiser when recording the nth tree so cruiser knows to measure DBH, height, etc.  Complete settings below to define the sampling type field and values representing the different supported sampling types"
• Stand-Level Sample Type Field
  • Name of field in the Stands table that stores the type of sampling (if any) should be used for a given plot.  Default field name is 'Sample_Type'. MobileMap expects that this field will use a coded value domain with the following values for supporting sampling types: BB = Big BAF, STR = Sample Tree Ratio, FTN = First Tree North, PCM = Point Count or Measure, None = no sampling."
• Plot-Level Sample Type Field
  • Name of field in the Plots table that stores the type of sampling (if any) should be used for a given plot.  For 'Point Count Measure' approach, sample type at the Stand level will be used to set plots to Count or Measure.  Default field name is 'Sample_Type'. MobileMap expects that this field will use a coded value domain with the following values for supporting sampling types: BB = Big BAF, STR = Sample Tree Ratio, FTN = First Tree North, PCMC = PCM Count, PCMM = PCM Measure, Tally = all trees tallied (same as PCMC, all trees counted and not measured) None = no sampling (same as PCMM, all trees measured)."
• Tree-Level Sample Type Field Name and Values
  • Name of field in the Trees table (field name should be different than plot-level sample type field) that stores whether tree is a Measure tree or a Tally tree, and the values representing 'measure' and 'tally'. Use colons to separate 3 components.  Typically the values will come from a coded value domain assigned to this field.  Default field name is 'Sample' and values are 'M' and 'T' (e.g., 'Sample:M:T',without quotes).  Note, cannot use non-nullable fields for fields like DHB or Height, since tally trees do not require these measurements (Species and Tally or Count can be non-nullable).

Settings > MobileMap Cruise > Stand & Plot Summaries

• Enable Calculation of Stand 
  • Check box to enable calculation of stand summaries including BA, TPA and QMD
• Enable Calculation of Plot Summary
  • Check box to enable calculation of plot summaries including BA, TPA
• Minimum DBH for average tree per plot calculation
  • Minimum DBH for determining if a tree should be included in the average tree per plot calculation in stand summary.  Default is zero, increasing this value can prevent small trees from having strong impact on average trees per plot calculation."
• Nested Plots
  • Check box to indicate that a nested plot design is used.  Nested plots are small fixed radius plots used to measure smaller trees.  Use the fields below to indicate the DBH cutoff and area of the nested plot"
• BAF Limiting DBH
  • Minimum DBH of trees measured on variable radius plots when nested plot design used
• Nested Plot Area
  • Area of nested plot in fraction of an acre.  For a 1/200th acre plot (radius 8.33 ft) use '200' (no quotes)"

Settings > MobileMap Cruise > Volume Calculation

• Tree Volume Database File Name
  • Name of the SQLite database file name to use when calculating volumes (default is 'fvs_nvel_volume.sqlite') and 'dubbing' tree heights.  Database file should be stored in folder named 'Volume' in the main data directory (e.g., '/storage/1234-5678/MobileMap/Volume')
• USFS Region
  • Select the USFS Region for volume calculations
• USFS Forest
  • Enter the nearest USFS Forest 3-number code (e.g. 103 for Bitterroot National Forest) for volume calculations.  If volume database created using Region default rather than forest-specific equations, use '1' (no quotes) for region.
• Volume Unit
  • Select the volume unit to use when calculating tree volumes.

Overview

MobileMap Harvest is an extension of MobileMap that is specifically designed for use in the cab of harvesting machines such as feller bunchers.  It works in conjunction with the MobileMap Harvest Module, a separate device that connects to the machines power and harvesting controls and records the time and location of each tree that is harvested.  MobileMap Harvest was developed in close cooperation with The Nature Conservancy and includes licensed TimberGuide® technology (Genesis Industries, LLC).

Compnents and Installation

Installation of MobileMap Harvest is behond the scope of this document.  This guide assumes that MobileMap Harvest has been installed in a feller buncher, including the following components:

• GPS - High accuracy GPS reciever with roof mounted external antenna protected by a rigid cover.  The GPS should include onboard processing of high accuracy GPS locations without the need for post-processing or network connectivity.  The GPS should support Bluetooth connections from Android devices.  GPS with integrated antenna and processing units (e.g., Juniper Geode, SX blue F90 ) are not suitable for MobileMap. 
  • Candidate GPS units include:
    • EOS Arrow 100 https://eos-gnss.com/product/arrow-series/arrow-100
    • SX blue II+ GNSS https://sxbluegps.com/products/gps-gnss-receivers/
    • Trimble R1 (with external antenna) https://www.trimble.com/R1-GISUser.aspx
  • The GPS should be mounted to the cab and have a wired power connection (rather then external battery that will require frequent charging).  Follow directions from the GPS manufacturer to install and configure the GPS, including downloading and installing any Android applications that are needed to connect the GPS to the Android tablet and for the Android operating system to access that device information as a 'mock location' that is available to applications such as MobileMap.
• MobileMap Harvest Module - The Harvest Module should be mounted to the cab and connected to vehicle power and to the harvest trigger circuit (typically the accumulator arm of a feller buncher).  It should be in view of the operator so that the indicator lights can be used to help verify that the device has power and is properly responding to tree harvest events.
• Android tablet mount - The MobileMap Android tablet should be secured to a rugged mount such as a RAM mounting system and the tablet connected to vehicle power for continuous charging
• MobileMap application and data - before installing and testing in a harvester, ensure that the most recent version of MobileMap has been installed and licensed, that an appropriate feature service has been selected and initialized, and that settings stored on the feature service have been imported.  Also make sure that suitable base map data have been packaged and stored into a project folder on your device's MicroSD card.  It is a good idea to test connectivity to the GPS and MobileMap Harvest model prior to installation in a harvester to debug any issues with the software or hardware prior to installation.

MobileMap Configuration

Once all MobileMap Harvest components have been installed and powered up via vehicle power sources (not battery), use the following steps to configure MobileMap Harvest:

• Open MobileMap and verify that key settings have been applied (they should have been imported from settings after the feature service was initialized).  Specifically, ensure that the following settings have been applied.  If you don't know what values to use for these settings, leave the default values, as they likely are suitable or have been set via the settings stored in the feature service being used for harvest.
  • Situation Awareness
    • Enable Situation Awareness Panel (checked)
    • Situation Awareness Polygon Layer (name of layer to be used to provide situation awareness)
    • Situation Awareness Fields To Display (comma separated list of attributes to display in the situation awareness panel)
  • MobileMap Harvest
    • Enable Automated Harvest Mapping (checked)
    • Harvest Trees Location Feature Layer (name of point layer to record harvest tree locations)
    • Harvest GPS Location Feature Layer (name of the point layer to record GPS locations at time of harvest (useful for debugging GPS and orientation issues)
    • Harvest Minimum Speed for Bearing (critical for filtering out noisy GPS-derived orientation information)
    • GPS Bearing Field (name of field that can be used to store the GPS-derived orientation that was used to calculate the harvest tree location - helpful for calibrating the Harvest Minimum Speed setting above) 
    • Harvest GPS Offset (the distance in feet between GPS antennae and harvester cutting head
    • Harvest Data Read Interval (in milliseconds - default is 1,000)

MobileMap Harvest Operation

Recording Tree Harvest Locations

Once MobileMap Harvest has been properly configured, operation is very straight forward.  The Harvest Module will automatically detect each tree event by sensing the current on the wire coming from the harvester button (e.g., accumulator arm trigger button).  That signal will be temporarily stored on the Harvest Module, until it is read via Bluetooth by MobileMap.  MobileMap will repeatedly try to read data from the Harvest Module whenever it is powered on and connected via Bluetooth.  If it finds a tree harvest event, it will read the most recent GPS coordinates and orientation from the connected GPS unit, and use these to project out to where the location of the harvested tree was.  It will then create a new tree point using the projected coordinates and save the tree record, issuing an audible beep to let the operator know that the data was captured.  There are no actions that an operator needs to take in order to record tree harvest events or locations.

Situation Awareness

In addition to recording tree harvest locations, MobileMap includes a situation awareness panel to help inform operators what harvest polygon they are located in, and what the perscription is for that polygon.  When the situation awarness panel is enabled, MobileMap will display the color of the polygon that the harvester is currently within, as well as a text message composed of one or more attributes from that polygon. 

MobileMap provides several methods for automated and manual data backup and reocvery.  These tools are intended to prevent data loss in the event of a mobile device failure.  They are not intended to provide offline workflows for data management, but can be used to help protect data prior to data upload when data upload will be delayed due to lack of internet access.

Settings

Backup Interval - Automated data backup is currently only enabled for MobileMap Cruise, as it is triggered by save of specific cruise features such as stands, plots or trees.  If not using cruise functionality, use manual backup to save data.  If automated backup of cruise data is desired, enable this in MobileMap settings by setting the backup frequency (Settings > MobileMap Cruise > General > Database Backup Interval) to the appropriate interval (e.g., every plot save operation, every stand save, every 10 trees, etc.)

Backup Format - The default backup format is a single text file, containing JSON data which includes only the new and modified features (see description below).  An alternative SQLite database format is also available (see description below) and can be enabled in settings (Settings > MobileMap > General > Data Backup in SQLite Format).)

Backup File Location

All backups will be stored in an 'Export' folder in the selected Data Directory.  MB&G recommends the use of MicroSD cards for MobileMap base data and thus for the Data Directory.  By using MicroSD card, automated backups will be stored on external media that can be removed is a device is damaged in the field.  When automated backups (MobileMap Cruise only) are used with a MicroSD card, it is possible to recover all data collected during the day even if the mobile device is damaged at the end of a day (e.g., dropped in a stream) by removing the SD card, drying the SD card off and inserting it into a PC, accessing the most recent backup file (e.g. JSON text file) and uploading the new/modified data to the feature service by cutting and pasting into a browser.

Export Feature Data

In addition to the automated backup described above, data can be backed up manually (Actions > Export Database).  This may be necessary in situations where a device is damaged and no longer able to access the internet (and thus cannot upload) or if upload errors cannot be resolved.  One situation where this can occur is when features have been deleted on the server (e.g., by InventoryManager) then a MobileMap users modifies those feature and tries to upload their changes.  In this case, the change cannot be applied, because the feature does not exist in the service.  It is possible to export these data and manually load them into the service. 

Export of JSON data:

This approach is the preferred (default) format for automated and manual backup of data from MobileMap.  This approach exports only the new/modified feature data and stores it in a single text file that contains a JSON representation of the Esri feature data.  It includes the links to the feature service endpoints for adding/updating data for each layer that contains new/modified features.  While it is intended for use by data managers, standard users can be trained to use this approach.

Because this approach exports only new/modified data, there are scenarios where the JSON files produced will not initially include the desired data.  Consider the case where a user successfully uploads data from MobileMap, then deletes those data using AGOL, InventoryManager, etc., but decides at a later time that they want to recover those data from MobileMap.  In this case, MobileMap will not see those data as new/modified, since they have not changed since they were uploaded.  One way to address this issue is to re-open and save each feature that needs to be recovered.  Simply opening and closting the tree list for each plot, for example should re-save the plot and all trees, and thus include these plots and trees in the JSON export file.

When data are exported to JSON format, they will be saved in the data directory's Export subfolder, in a file named MobileMap_XXXX_todays_date_incremental_backup_JSON.txt.  To load these data into the feature service, copy this file to a PC, open it using a text editor, and then load the data by copying in the JSON representation of the data into the matching feature service layer endpoint.  For example, if the file contains the following text:

Layer: Plots

Updates: 1
URL: https://services1.arcgis.com/ABCDEFG/arcgis/rest/services/Data_Model_v1/...
[{ "geometry" : {"x":-1.271745906241922E7,"y":5788956.715272526,"spatialReference":{"wkid":102100,"latestWkid":3857}}, "attributes" : {"Archived":null,"Big_BAF":"None","Created":1573845358349,"Created_Source":"MobileMap 4.3.7-standard","Cruiser_ID":"KQH","Design1_Size":"BAF20","Design2_Size":0.0,"Edited":1573866200609,"Edited_Source":"MobileMap 4.3.7-standard","OBJECTID":11,"Parent_ID":"{4743dc00-abcd-44c1-9bee-7a748ec24811}","Plot_ID":1,"Plot_Type":1,"Sale_Name":"Big Sale","Sample_Design":"BAF","Sample_Type":"None","Status":"Cruised","Unique_ID":"{aedd61a9-5f21-43ba-9981-71d75a359528}"}}]

To load the data above, open a browser and past into the address bar the URL (https://services1.arcgis.com/ABCDEFG/arcgis/rest/services/Data_Model_v1/...).  You might be prompted to log in if you are not logged into the site.  Next, paste in the data text string, which will start with [{ and end with }].  Click submit and note the success or error message(s). 

If the upload from MobileMap failed because the features had been deleted from the server, they will fail when attempting this process as well.  If you wish to re-create these features ni the service, change the URL from .../updateFeatures to .../addFeatures and then repeate the process to save these as new features.  

If the update (or add) failes due to a validation error, you may need to use a text editor to modify your data.  Consider the case where a feature service hosted in ArcGIS Portal was updated (overwritten) by a data manager and a data type was changed from Text to Integer.  The JSON data will still contain text values like "small", "medium", "large" while the new service will expect values like 1, 2 or 3.  Before the data can be saved in the service, they will need to be manually fixed to address this disconnect.

Export of SQLite database:

This approach produces a full SQLite database (all data, even data that has been downloaded from the feature service and is unchanged).  This approach can be useful if a large amount of data must be recoverd and the data have not been modified since they were uploaded.  In that case, they would not initially be included in the default JSON export format, and using the SQLite format would avoid having to re-save all features just to get them to export.  The SQLite format, however, is not a standard Esri offline geodatabase, it is a MobileMap-specific SQLite format.  This approach is for expert users as it requires knowledge of SQL/SQLite, and a SQLite viewer/editor (e.g., DB Browser for SQLite https://sqlitebrowser.org/).  MB&G can provide instructions for recoving data from this SQLite file to data managers if needed.  MB&G can also perform this data recovery as a service upon request. 

Export Cruise Data

Export Cruise data to CSV files:

Similar to the Cruise Export functionality in InventoryManager, this approach exports cruise data as 3 CSV files containing the attributes (not spatial data) for Stands (Cruise Units), Plots, Trees.  This approach is typically used by users who want to transfer to a PC to run Excel functions for QA prior to data upload to the feature service.  This approach requires an export conifiguraton file (same format as the file used by InventoryManager for cruise export).  This file should contain all of the fields that need to be exported.  The export configuration file must be named 'cruiseExportMapping.csv' and must be stored in a folder named 'Export' that is within a MobileMap project folder on your device (e.g., SD card > MobileMap > MyProject > Export > cruiseExportMapping.csv).  More details on the format of export configuration file file can be provided upon request.

• Phone
  • Call our dedicated MobileMap support line +1 503-290-0542
  • If no one answers, please leave a detailed message
  • Voice mail checked regularly during work hours, Monday - Friday, 8am- 5pm (PST)
• Email
  • Dedicated email for software sales and support software@masonbruce.com

Note: When reaching out to our support team, please provide as many details as possible, including:

• MobileMap version (Actions > About MobileMap)
• Category of issue - what type of issue is it:
  • Device issue (e.g., GPS not working, screen turning off)
  • Base map data issue (e.g., imagery not showing or poor resolution)
  • Map display issue (e.g., labels not working, shapefile won't display)
  • Collection (e.g., unable to collect features, attribute field missing or read only)
  • Editing (e.g., unable to edit polygon geometry, unable to update attribute field)
  • Sync (e.g., errors when uploading or downloading) 
  • Documentation issue (e.g., missing or inaccurate documentation on a feature)
• Scale of the issue - how many users or devices are affected?
  • One device
  • Multiple devices
  • All devices in my organization
• Severity of the issue:
  • Critical - application crashes or causes loss of data
  • Major - loss of significant functionality, no workaround
  • Normal - moss of functionality, workaround exists
  • Minor - minor loss of functionality or cosmetic issue
  • Immediate - ASAP 
  • Next business day
  • In the next week
  • In the next month
  • In the next release

Creating Base Map Data for MobileMap

MobileMap utilizes two broad categories of data - operational data and base map data.  Operational data are stored in ArcGIS Feature Services and contain the data model for collecting and editing data.  These data are uploaded and downloaded from the feature service when a user is online.  Base map data, on the otherhand, are read-only data layers that provide background imagery and related data (e.g., ownership boundaries, streams, roads, etc.).  MobileMap supports a range of file formats for base map data, including Esri Tile Packages (TPK), Esri Compact Tile Caches (CTC), MBTiles databases (MBTiles), Shapefiles (SHP) and Comma Separated Value (CSV) files.  The most common formats used in MobileMap are TPK and SHP, and creation of these files are described in the sections below.

TPK Creation

Esri Tile Packages (TPK) are tiled images stored at multiple zoom levels.  The zoom levels follow the standard Esri/Google/Bing tiling system which is best described here .  This tiling system uses the Web Mercator projection and zoom levels range from 1 (lowest resolution, whole earth stored in 4 tiles that are 256 pixels x 256 pixels each) to 23 (highest resolution, each pixel represents 1.87 cm of the Earth's surface).  There are several ways to create TPKs, including in ArcMap, ArcGIS Pro and MobileMap.  The sections below describe the process for creating TPKs in ArcMap and MobileMap.

NOTE:  The TPK format is very similar to Esri's lesser known Compact Tile Cache (CTC format) mentioned above.  In fact, a TPK is merely a Zipped folder containing a CTC, along with some related metadata.  In the early days of of MobileMap (circa 2013) we routinely converted TPK file extensions to .zip, unzipped them, and extracted the CTC.  There are small performance gains from using these unzipped data.  In recent years, with the advances in mobile device hardware, we have not found this step to be necessary.  If you are using very large TPKs and seeing a performance issue when loading or panning base map data, reach out to our support team for instructions on how to create and use CTCs instead of the easier to use TPK format.

Creating TPKs in ArcMap

NOTE:  As of ArcMap version 10.2, it is no longer possible to create tile packages (TPKs) that contain ArcGIS Online hosted base maps.  Prior to ArcMap 10.2 (e.g., ArcGIS 10.1) it was possible to include these data as inputs to tile packages.

Steps for creating a TPK in ArcMap

• Open a map document in ArcMap.  Change the coordinate system of the data frame (“Layers” in the example below) to WGS 1984 Web Mercator (auxiliary sphere).  This option is found under Projected Coordinate Systems -> World -> WGS 1984 Web Mercator (auxiliary sphere). 

• Add base map data as needed from existing imagery or other inputs.  Note that raster data that are not from streaming services should be projected into WGS 1984 Web Mercator (auxiliary sphere) coordinate system before adding them to the map when creating TPKs. Vectore data, including points, polylines, polygons from Shapefiles or Feature Classes, do not need to be re-projected as long as the data frame projection has been set to WGS 1984 Web Mercator (auxiliary sphere).  ArcMap will project vector data as needed (on-the-fly) when building the TPK.
• Set the symbology (colors, display scale levels, labels, etc) for all layers.
• Add metadata to the Map Document Properties (File -> Map Document Properties) Summary and Description boxes (this is required for the Create Map Tile Package Tool) and save the map.

• Open the ‘Create Map Tile Package’ tool.
• Select the map document you want to cache (make sure the data frame shows the entire area you want to cache) and that you have saved the MXD since your last change
• Select the name for the output file (it will be a tpk file format)
  • We recommend using a naming convention that includes the zoom level (see next step) as well as the source or type of data (e.g., Oregon_NAIP_2017_L18.tpk)
• Set the level of detail to the desired level. Level 16 to 17 is standard for forestry work, while a higher level like 19 might be more appropriate for wetlands work.  
• Click OK to run the tool. 

• After the tool completes its process, navigate in Windows Explorer to the folder where you saved the output .tpk file.
• Follow steps below to store the TPK you created into the correct directory structure for use in MobileMap.

Creating TPKs in MobileMap

Note: This functionality is not available if your organization uses Portal for ArcGIS.

MobileMap includes a Download Base Map tool as a convienient method for obtaining base map data, including imagery and topo maps.  When downloading TPKs from the Download Base Map tool, MobileMap is accessing the 'export' function from Esri's base map services.  This functionality is limited to a maximum number of tiles, and there are additional practical limits on total file size of an exported TPK file.  Keep in mind that the size of a TPK is a function of the extent and the maximum zoom level.  For large base maps (e.g., high resolution imagery for a whole county or state) use ArcMap and an imagery source that you have local access to (e.g., a download of NAIP data).  If you need high resolution data for a demo or small project, use this approach and a high zoom level (e.g., 19) but limit the spatial extent of your download to a very small area.  If you want to have a large basemap just to serve as a frame of reference, use a large extent but limit the maximum zoom level to a very low level (e.g, 6 or 8).  While there is no hard rule on the maximum extent or zoom level combinations that are supported, we have found that TPKs larger than 100 MB in size do not always create or download property.  To be safe, try to limit the size of downloaded TPKs to under 50 MB.

In addition to the caveates above, there is one additional problem with TPKs generated via this tool - they include a maximum zoom level parameter in their metadata.  This parameter causes the TPKs to disappear if you zoom in beyond that zoom level.  So, rather than getting pixelated or blurry, they simply disappear.  In many cases this is not the desired behavior.  TPKs created in ArcMap (process described above) do not have this limitation.  If you want to use the Download Base Map tool in MobileMap but do not want your TPK to disappear at higher zoom level, there is an optiona step that can be performed to remove this maximum resoluton parameter from the TPK file, but it is a bit complicated.  See the optional instructions at the bottom of this section for more details.

To create TPKs in MobileMap use the Download Base Map tool by following these steps:

1. Sign in to ArcGIS (Actions > SIGN IN TO ARCGIS)
2. Open the Dwnload Base Map tool (Actions > Download Basemap)
3. Select the layer you would like to download from the dropdown list
4. Pan and zoom the map to the desired extent
5. Select the maximum zoom level that you would like to download.
6. Select DOWNLOAD
7. When the download completes, note the directory where the file was downloaded.  Typically this will be the Download folder on your internal storage
8. Use a file manager (e.g., MyFiles, Astro, etc.) to copy the TPK to a map cache's TPK folder (see instructions below for more information about file structure)

Optional - If you want to use the Download Base Map tool in MobileMap but do not want your TPK to disappear at higher zoom level follow the steps below to enable "overzoom" within a TPK:

• After step 7 above, and before saving your file into it's final destination you will need to modify the TPK
  • Copy the TPK to a PC where you have access to a Zip file creator application (e.g., 7-Zip) and a text editor
  • Rename the TPK file extension from *.tpk to *.zip
  • Unzip the file using any unzip tool (default Windows capability fine for this step)
  • Navigate within the resulting folder to \servicedescriptions\mapserver
  • Open the mapserver.json file in a text editor and do the following
    • Search for the text "maxScale"
    • Wherever this property exists and is not set to zero (typically only in 1 place, the 6th instance of "maxScale", the last property in the "contents" property) it will be set to the map scale that cooresponds to the zoom level you selected when building the TPK.  For example, if you selected zoom level 15, you will find one or more instances of  "maxScale": 18055.95 which indicates that the maximum map scale is 1:18,055.
    • Replace all instances of this with the map scale for zoom level 23, using: "maxScale": 70.53.  This will tell MobileMap (or any Esri software) that this TPK should be desplayed at all resolutions, instead of hiding these data at resolutions higher than the resolution they were created from.
    • Save the modified file mapserver.json
  • Re-zip the folder using your Zip application (e.g., 7-Zip), setting to no compression (e.g., compression format = 'storage').  This step is important, we don't want to actually compress the data, we just want to contain it into a single zip file.  If compression is used the resulting file will not be readable by MobileMap or any Esri software.
  • Replace the *.zip file extension back to *.tpk
  • Copy the zip file to the correct destination folder in MobileMap (e.g. sdcard/MobileMap/myproject/TPK) and test to verify that you can now "overzoom" the TPK

MobileMap Directory Structure

• The folder structure for MobileMap can be created directly on your mobile device, or can be created on a PC, then copied onto the device
• Start by creating a parent MobileMap data folder called MobileMap.
• Within the MobileMap folder create one subfolder for each project or 'map cache'.  Some users create new map cache folders for each geographic area where they work.  Other users create different map cache folders for different types of work, based on the base map data they like to have displayed when performing that work.  Still others use a single map cache for all of their work.  The strategy will depend on the volume of data that you need, the number of distinct geographic areas where you work, the degree to which larger work areas are separated into regions or other groups, etc.  For this example we will create two map caches, one for Washington and the other for Oregon.
• For each map cache folder (e.g., sdcard\MobileMap\region1), create two subfolders, TPK and SHP.
• Add shapefiles to the SHP folder and TPKs to the TPK folder. Note that Shapefiles must be projected into WGS 1984 Web Mercator (auxiliary sphere) to display correctly in MobileMap.

• Repeat the steps above to create additional map cache folders and add in the necessary Shapefiles and TPKs
• Optionally, create an additional map cache named 'Default' and include the same two subfolders: TPK and SHP
  • The default map cache can be used to store any data that should be used as a base map for all projects.  Typically a very large extend but low resolution TPK is stored in sdcard\MobileMap\Default\TPK to provide a common base map for all MobileMap use.  An example might be the entire continent at zoom level 6, or an entire state at zoom level 8
• Once the data are correctly organized, copy the MobileMap folder from your desktop to the root folder of your SD Card. Removing the SD card from your device and using a USB to micro SD card adapter in your PC will be the fastest way to transfer data to the SD card, although data can also be copied over a USB cable
• Below are examples of a typical file structure on an SD card for MobileMap.  The example below has two map Caches (OR and WA), each with 2 TPKs, and 2 Shapefiles. 

MobileMap Root Directory

Map Cache Directory (OR or WA)

SHP Folder Structure

TPK Folder Structure

CREATING AND PUBLISHING A FEATURE SERVICE

ARCGIS MAP DOCUMENT

• Open a blank or existing ArcMap document. (This can be any ArcMap version 10.0+)

• Change the Data Frame (Layers) coordinate system to WGS 1984 Web Mercator (auxiliary sphere).

• Add all Feature Classes. These feature classes will be templates for your field data layers. 

• Each feature must be projected to WGS 1984 Web Mercator (auxiliary sphere).  (MobileMap and ArcGIS Online only reads WGS 1984 Web Mercator (AS) projection)

DATA MODEL

The data model for MobileMap is defined in an ArcGIS Feature Service, which is typically created by designing a data model using an ArcGIS File Geodatabase and then publishing that feature service from ArcMap or ArcGIS Pro.  Data modeling in ArcGIS is a complex topic and requires some knowledge of Esri data types, Coded Value and Range Domains, required fields, etc.  MB&G recommends that you start with a template that we provide, and then modify that as needed to incorporate your specific data requirements. 

• General Approach
  • Check the MB&G Template for your industry specific Data Model. MB&G recommends using (or at least starting with) a standard Data Model and Domains for a successful MobileMap experience.
  • Turn ON Editor Tracking for all layers in ArcMap (or ArcGIS Pro) prior to publishing your feature service.  Editor tracking is required for MobileMap to properly sync with the feature service.  Editor tracking must be enabled on all layers prior to publishing - it is not possible to enable editor tracking in ArcGIS Online for use with MobileMap.
  • To turn on Editor Tracking 
    • In ArcCatalog, naviagte to the geodatabase which contains all feature classes. 
    • Right click each feature class below the database and Select 'Manage'. 
    • In the 'Manage' menu, select 'Enable Editor Tracking'
• Recording the user that created or last edited a feature
  • ArcGIS Online's Editor Tracking functionality will maintain some information about the ArcGIS User who created and last edited a feature.  It is important to note a few caveates with this capability
    • ArcGIS Online will record the date/time that the feature was saved to ArcGIS Online, not when it was saved in the field.  If a user collects or edits on a Monday, but doesn't upload until Friday, ArcGIS will record the date/time of creation or modification as Friday
    • Republishing a feature service with existing data in the File Geodatabase will change all created user and created dates to the user who is publishing the service and the date/time that the service was published, overwriting the original user and date/time for each record
    • To address these limitations, MB&G recommends using seperate fields for managing this important information
      • Observer - typically a 3-4 character Text field that records the initials of the user collecting or editing the data.  There are two settings in MobileMap (Settings > Data Model Settings > Observer Field, Settings > Data Model Settings > Observer Initials) which can be used to set the name of this field (the default is 'Observer' but other values like 'Cruiser_ID' can be used for the field name) and the initials of the device user.
      • Created - Date field that MobileMap will use to record the data/time at which a new feature was created in MobileMap.  This field will NOT be overwritten by ArcGIS when data are uploaded.  The name of this field can be changed in MobileMap settings (Settings > Data  Model Settings > Custom Created Date Field Name, default value is 'Created').
      • Edited - Date field that MobileMap will use to record the data/time at which an existing feature was edited in MobileMap.  This field will NOT be overwritten by ArcGIS when data are uploaded. The name of this field can be changed in MobileMap settings (Settings > Data  Model Settings > Custom Edited Date Field Name, default value is 'Edited').
      • Created_Source - Text field that MobileMap will use to record the MobileMap version that was being used when a new feature was created in MobileMap.  This field can be very useful if muliple applications are being used to create data (e.g., ArcMap, ArcGIS Pro, ArcGIS Online, MB&G Spatial CMS, MB&G InventoryManager) as it will identify if MobileMap was the application that created a particular feature.  It can also be useful in debugging if issues arise during data collection, as data managers can see if an issue is only occuring on a certain version of MobileMap.  It can also help device managers keep track of what versions of MobileMap are being used in the field.  The name of this field can be changed in MobileMap settings (Settings > Data  Model Settings > Created Source Field Name, default value is 'Created_Source').
      • Edited_Source - Similar to Created Source, this Text field records the the MobileMap version that was being used when an existing feature was last edited. The name of this field can be changed in MobileMap settings (Settings > Data  Model Settings > Edited Source Field Name, default value is 'Edited_Source').

SYMBOLOGY

Getting the correct Symbology for MobileMap is a critical step to view your data. MobileMap only handles Simple symbols types for Point, Lines and Polygons. 

For point features, 

• In your Map Document, double click on the point symbol to open symbol selector window. 
• Select  'Edit Symbol'

• After clicking on Edit Symbol, ensure the type is set to 'Simple Marker Symbol'. 
• Select the style of the symbol from the drop down for Style. 

• Once the Symbol is selected, Click on save.
• Similar to points, lines must use Simple Line Symbols and Polygons must use Simple Fill Symbols.
• Similar steps are to be performed for Lines and Polygons. (Note that Lines and Polygons can only have solid or dotted Style).

PUBLISHING TO A FEATURE SERVICE

Once the symbology, projection, data model and Editor Tracking is set and saved, follow the steps below to publish the map document as a feature service in ArcGIS Online. 

• Make sure to zoom out to an extent that covers all of the area for the relevant data to be published. For example, if you have data which consists of all counties in California, zoom out on the map to show California, Oregon and Mexico.
• Once zoomed out, save the map document and do not zoom back in before publishing.
• Ensure that you are logged in to your ArcGIS Account in ArcMap. To login, go to File -> Sign In, or go to www.arcgis.com to create an account.
• Share the feature service by navigating to File -> Share As -> Service.  Select ‘Publish a service’ and name the service (pick a short name, all lower case with no spaces). Work your way down the left panel.
  
  • Under Capabilities, check Feature Access and uncheck Tiled Mapping.  
  • Under Feature Access, check the boxes next to Create, Delete, Query, Sync, and Update.  (Figure 11)
  • Under Item Description, add text in the Summary and Tags. 
  • Under Sharing, choose the level of Sharing.  Selecting Everyone makes the feature service a ‘public’ service, meaning anyone could potentially find the service if they know what to search for on ArcGIS Online.  Selecting your organization limits the sharing to just your group. (If you select your organization, you will need to put your ArcGIS Online user name and password in the settings of MB&G MobileMap).  
• Finally, select Publish in the upper right corner.

Your feature service is now published.  Log in to ArcGIS Online to review and confirm it is as expected.

Users may now access the feature service using MobileMap. Detailed instructions for accessing feature services in MobileMap can be found in the Quick Start Guide

https://mbgmobilemap.com/quick-start-guide-standard

OTHER WAYS TO GET BASEMAP IMAGERY

- DOWNLOADING IT WITHIN MOBILEMAP

- HIGH RES IMAGERY DOUBLE CACHING

Contact MB&G for details on how to obtain basemap imagery from MobileMap or double caching

• Phone
  • Call our dedicated MobileMap support line +1 503-290-0542
  • If no one answers, please leave a detailed message
  • Voice mail checked regularly during work hours, Monday - Friday, 8am- 5pm (PST)
• Email
  • Dedicated email for MobileMap mobilemap@masonbruce.com

Overview

While many MobileMap users take advantage of ArcGIS Online as their ArcGIS implimentation, MobileMap works great with Portal for ArcGIS as well.  Nearly all MobileMap functionality are compatible with Portal.  The few exceptions currently are 1) the ability to download base maps directly from ArcGIS Online, and 2) support for turn-by-turn driving directions.  These functions require that users authenticate with ArcGIS Online in order to access these services.  When MobileMap users sign-in via Portal, they are not signed in to ArcGIS Online, and thus these features are not available.

Registering MobileMap with Your Portal Instance

In order to use MobileMap with your Portal instance, it is necessary to register MobileMap as an application that can authenticate with Portal.  This can be done by going to Content > Add Item > An Application.

• On the 'Add an application' form, select 'Mobile', 'Ready to Use' and 'Android'
• Add the following URL: https://mobilemap.mbgapplications.com/
• Set the title to 'MobileMap'
• Set 'MobileMap' as a tag, and add any additional tags that will help administrators search for this item
• Click 'Add Item'

• When the new item is created, go to settings, and scroll down to the bottom of the page and click 'Register'

• On the Register form select 'Native' for App Type
• Enter the following Redirect URI: urn:ietf:wg:oauth:2.0:oob
• Click 'Add'
• Click 'Register

• The item will now display the App ID.  Copy this and use it as the 'Client ID' in the MobileMap authentication Settings below.

Configuring MobileMap Authentication Settings

Once you have registered MobileMap with your Portal, you will need to configured MoibleMap settings to use your Portal:

• Open Settings > Authentication
• Check the box for 'Use Portal for ArcGIS
• in 'Portal for ArcGIS Name' select a name (sed as a title for the sign-in form to help remind you that you are signing into Portal and not ArcGIS Online)
• In 'Portal for ArcGIS URL' enter the URL to your Portal
  • e.g., https://gis.mystate.gov/portal
• In ' Portal for ArcGIS Client ID', enter the Client ID that was created by Portal when you registered MobileMap (see details above)

Sign in to Portal

Once you have registered MobileMap with your Portal, and configured MoibleMap settings, sign-in to your Portal by doing the following:

• Open the Actions Menu
• Select 'Sign in to ArcGIS'
  • Enter your Portal username and password
  • Tap 'Sign In'
• If you see a blank form instead of a sign in form:
  • check to make sure you have an interent connection
  • Verify the Portal URL and Client ID in settings (see details above)

* Note that for typical daily authentication (e.g., upload/download) it is possible to use credentials stored in Settings > Authentication > ArcGIS Username and ArcGIS Password.  Portal sign-in described above is typically required only for refreshing the list of available feature services when selecting a feature service (Actions > Select Feature Services).