Starting Point

When an existing Feature Service has been developed by MB&G or LandMark it will be provided to you as a File Geodatabase (FGDB) and an ArcMap

...

Once the data model has been created Document (*.mxd) or ArcPro Project (*.aprx). Additionally, you may be provided with ArcGIS Layer files (*.lyr) which define the symbology for feature layers. If business rules (Rules, Related_Domains, Check_Rules) have already been developed, they will be stored in the FGDB. The steps below can be used to publish the Feature Service from these inputs. If you have developed the data model independently, the steps below can be used to develop an ArcMap Document or ArcPro Project and publish a Feature Service.

ArcMap / ArcPro Settings

If developing a ArcMap Document or ArcPro Project from scratch, add all Layers and Tables to your Map in ArcMap or ArcGIS Pro, then adjust the settings, layer order and symbology using by following the information steps below.

Map Document / Project Settings and Properties

• Map document name - we recommend using the same name as the feature (e.g., Cruise_Data_Model_v2). This is helpful when overwriting a Feature Service, as ArcMap will know which Feature Service you are attempting to overwrite.

• Map Layer - set projection to Web Mercator (Auxiliary Sphere)

• Map Document Properties

  • Required properties - you must supply the following attributes prior to publishing

    • Title - We recommend using the same name as the MXD and Feature Service name

    • Tags - We recommend using ‘MobileMap’ and optionally ‘InventoryManager’ (if relevant)

  • Optional properties -

    • Summary - Use as appropriate to clarify the intended use of this service

    • Description - MobileMap settings can be copied from a MobileMap settings file (Actions > Export Settings)

Layer Order

The typical layer order is as follows:

...

Once a feature service is published, it needs to be shared to one or more groups in order for users to find that service in MobileMap’s Select Feature Services tool.

Create New AGOL Group

In order for MobileMap to find a Feature Service using the Select Feature Service tool, it must be shared with one or more groups to which the user is a member.

• If an appropriate group does not yet exist, create a new group, then invite users to join that group (see section below).

• When creating a new group in AGOL, it is necessary to set the content editing rights for the group. In order to invite users from outside your organization, it is necessary to select the option to allow users to update their own items. Therefor, under the question ‘What Items in the group can it’s members update?’ select ‘Only their own items. Note that this applies to AGOL items, not data. Users will be able to add/edit/delete data that are created by other users, but they won’t be able to edit AGOL items (e.g. Feature Services).

Invite a Users to an AGOL Group

...