Map Administration

In order to use LRM Web there are some basic map publishing tasks to consider.  These tasks can be accomplished using ArcGIS tools.  

Publish a Map

ArcGIS GIS Server is required to enable map services.  ArcGIS GIS Server is offered in three editions - Basic, Standard, and Enterprise.  For LRM Web editing you will need ArcGIS GIS Server Standard.  

Publishing your map as a map service to an ArcGIS Server site is a way that you make maps available to the web. 

While you can publish maps using either ArcMap or ArcGIS Pro, ArcGIS Pro seems to be more stable and reliable in publishing. 

Before you Begin

Here are some important tips to get the best performance out of your published layers:

1. Make sure your version of ArcMap or ArcGIS Pro is at the same release level as LRM Web.  See installation guide to determine which version is supported.

2. To improve initial drawing speed we suggest you set your map extent of the published feature service to a single feature.  This will improve the initial loading time of your map service. To set your extent:  

   1. Simply select a tabular record and zoom to it. 

   2. Save your layer before publishing.

3. We also recommend that you use scale dependent rendering.

Publish Map in ArcMap (NOT SUPPORTED AFTER Release 6.0)

Before publishing the map, register the database with the ArcGIS Server.  Right-click at the ArcGIS Server connection and click “Server Properties…” to open the ArcGIS Server Properties dialog.  Click the “plus” button to register a database. Data registration provides the server with a list of locations for your web services' source data. Data registration helps you validate that your services will reference data locations known and approved by the server administrator.

After you have prepared an mxd in ArcMap, you can publish the map as a service (File > Share As > Service > Publish Service) to your ArcGIS Server site.

If the published map is for viewing only, check “Mapping”.  If you allow editing on the published map, check also “Feature Access”.  For a map that has route event layers, you must check “Feature Access” in order to see the route event positions updated on the map after you have updated the locations on the Data View. See also the ArcGIS Pro section. 

Click “Analyze” to check for potential issues with publishing this mxd.  Note: If you cannot resolve the errors found in this analysis, please try to publish the same map in ArcGIS Pro. There is a chance that the same map may be analyzed and published successfully in Pro even though there are unresolvable errors in ArcMap. 

Click “Preview” to preview the published data. If everything looks good, click “Publish” to publish your map as a map service.

You can review your map service in ArcGIS Server Manager. 

To make sure the date fields display the value in your time zone, specify a time zone for the published maps in ArcGIS Server Manager after the map is published via ArcMap. This makes sure that the date fields in the Identify popup will display the time in your time zone.

Publish Map in ArcGIS Pro

The following steps will guide you on how to publish a map using ArcGIS Pro:

1. In ArcGIS Pro, load the layers you want to publish on a map.  

2. On the Catalog pane Favorites tab, add the ArcGIS Server via “Add Item”.

3. After the server is added, right-click on the server name and “Add to Project”.  It will appear under “Servers” on the Project tab.

4. To publish the map, right-click on the server and click “Publish \ Map Service”.

5. Select the map to be published.

6. Then, this Publish Map Service pane will appear.  On the General tab, specify the name for the map service.
   
   Under the “Shared With” section, check your organization. Check “Everyone” only if you want to make the layer public.  See Published Layer Security section below.

7. On the Configuration tab, check the capabilities.  If the published map is for viewing only, check “Map”.  If you allow editing on the published map, check also “Feature”.  For each checked capabilities, click “Configure Service Properties” to specify the properties.  

8. For a map with route event layers, you must check the “Feature” capability in order to see the route event positions updated on the map after you have updated the locations on the Data View.  If “Feature” capability is not checked, the route event layer will be published as a static layer which will not reflect the latest changes in the event table.   Click the “Refresh Current Layer” button (under “Viewing Tools”)  if you do not see the updated positions on the map, especially if you have modified the location values in the split data view below the map view.
   
   Note: If the published service contains polyline layers (e.g. Road) with m-values, please check “Allow geometry updates without m-values” so that you can use the Link tool to assign a Temp Graphic (which does not have m-values) to become the shape of a polyline feature. 

9. Click the “Analyze” button to identify potential performance bottlenecks and errors.

10. If there are errors, double-click on the error for help.  In this case, a “Register Database” dialog is opened.  Click “Create” and register the database.

11. Then, “Analyze” again.  Repeat this process until all errors are gone. 

12. Click “Publish” to publish the map.

13. Specify a time zone when you publish a map in ArcGIS Pro. If you publish in ArcMap, you can set the time zone in ArcGIS Server Manager after publishing the map.  This makes sure that the date fields in the Identify popup will display the time in your time zone.

14. Note:  Starting from ArcGIS Pro 2.4.3, you can publish map services to a standalone ArcGIS Server.  Previously, ArcGIS Pro can only publish map services to a standalone ArcGIS Server 10.6 (and higher) via ArcPy scripting (i.e. not publishing directly in the ArcGIS Pro application).  

15. Optionally, after publishing the map, go to ArcGIS Server Manager and uncheck “Filter web content” (Capabilities \ Feature Access \ Advanced Options).  This allows you to update an attribute with an XML, e.g. you have configured an overlay with a MAPCONTROLXML() SourceValue function.  If “Filter web content” is checked, setting an attribute with an XML will cause an 'Invalid untrusted Html content detected in field’ error.

16. If you have not checked “Allow geometry updates without m-values” when you publish a map that contains polyline layers with m-values, please check it here in ArcGIS Server Manager. This ensures that you can use the Link tool to assign a Temp Graphic (which does not have m-values) to become the shape of a polyline feature. 

Published Layer Security

To allow the users in your organization to access the published layers, check your organization under “Shared With” when you publish the map.  Or, you can modify the access level in Enterprise Portal or ArcGIS Server manager after publishing the layers. Unless you have made the layers public (i.e. check “Everyone”), you will be prompted to enter username and password before you can see the layers on the LRM web map.  To avoid the user entering the username and password every time the map opens, the map will read the proxy username (“portalProxyUser ”) and password (“lrmClientSecretKey”) from the AppSettings.json and load the layers. 

Publish Map Template in ArcGIS Pro

The following steps will guide you on how to publish a map using ArcGIS Pro:

1. In ArcGIS Pro, Insert a new Map template.

2. Customize your map template layout as needed and save it. (Dynamic text :- https://pro.arcgis.com/en/pro-app/2.9/help/layouts/add-and-modify-dynamic-text.htm) 

3. Once the template is saved. Open the Geoprocessing tool and search for the “Get Layout Template Info” tool.

4. Give the folder to the tool where the map template is saved. And run the tool. 

5. Search for “Export Web Map” tool.

6. Give the folder to the tool where the map template is saved and choose the layout, and run the tool.

7. Once the tool is successfully executed, then click on the History tab.

8. Right click on the “Export Web Map”. then, click on “Share As” and then click on “Share as a web tool”.

9. Then, this Publish Map Service pane will appear.  On the General tab, specify the name for the map service.

Under the “Shared With” section, check your organization. Check “Everyone” only if you want to make the layer public.  See Published Layer Security section below.

10. On the Configuration page, click on the “Synchronous” radio button under Parameters.

11. On the Content page, click on “Add Tool”.

12. Add “Get Layout Template info”.

13. Click on Analize. Resolve all the errors and click on publish. 

14. In Appsettings, please check the “mapPublishDetails” section for configuration.

Settings in AppSettings.json

The web Map View reads the settings specified in the AppSettings.json file. You have to edit the file directly, as no user-interface is available in this release to update the settings.  Below are the descriptions for the map-related settings:  

1. DataGroup: Module(Apps) ’s data group ID.

2. managedLayerURL - URL that contains the editable managed layers (Feature Layers).  A managed layer is expected to be named exactly the same as the display name of its corresponding context.  Please note that the road layer should be part of this URL if users are allowed to edit the roads. 

3. managedLayerCount - Number of editable managed layers to be loaded. For example, if “managedLayerURL” points to the published map and “managedLayerCount” is “3”, the map will load the first three layers in the published map, i.e. State, County and Tract.  If this number is bigger than the number of layers published in the managedLayerURL, the map will fail to zoom to the feature when it first opens.

4. managedReadOnlyLayerURL - URL that contains the read-only managed layers (Feature Layers), e.g. route event layers. A managed layer is expected to be named exactly the same as the display name of its corresponding context. Please note that the road layer will not be editable if it is included in this URL. 

5. managedReadOnlyLayerCount - Number of read-only managed layers to be loaded

6. geoprocessingLayerURL - URL that holds the geoprocessing layers (Feature Layers) for bizrule validation or overlay.  A geoprocessing layer is expected to be named exactly the same as the display name of its corresponding context specified in a Spatial BizRule table (TFM_SYS_BIZRULE*) or as specified in TFM_SYS_BIZSPATIALOVERLAY_WEB.OVERLAYLAYER_WEB. (This setting replaces the “overlayLayerURL” setting which exists in LRM 4.3 and before).

7. geoprocessingLayerCount - Number of geoprocessing layers to be loaded

8. baseLayerURL - URL that contains the base (background) Feature Layers, i.e. point, line, polygon, route event layers. 

9. baseLayerCount - Number of base layers (Feature Layers) to be loaded from baseLayerURL 

10. baseLayer2URL - A second URL for loading base (background) Feature Layers, i.e. point, line, polygon, route event layers. 

11. baseLayer2Count - Number of base layers (Feature Layers) to be loaded from baseLayer2URL

12. imageryLayerURL - URL that contains an imagery layer. 

13. imageryLayer2URL - A second URL for loading imagery layer

14. defaultBaseMap - Name of the default basemap from ESRI, e.g. “streets”

15. defaultMapViewCenterCoordinate - Coordinates (in lat/long) of the center point when the Map View is opened without a feature selected on the tree view. The default value is set to center around North America.

16. defaultZoomlevel - Default zoom level at which the Map View is opened without a feature selected on the tree view.  It represents the level of detail at the center of the view.  A small number (e.g. 3) is a small map scale, whereas a large number (e.g. 18) is a large map scale. 

17. mapStorageUnit - Define the unit of measure used to store spatial data in the geodatabase. Possible values: ‘METRES’ or ‘FEET’ (case sensitive).

18. maxMapSelectionCount - The maximum number of features which the map will select and highlight

19. portalProxyUser - The portal proxy username with which the map will automatically login before loading a portal feature layer.  The map will take the lrmClientSecretKey appsetting value as the password. Without this automatic login, the user will be prompted to enter username / password when the map loads a non-public portal feature layer.

20. arcgisPrintLayout - Default “Page setup” in the Print Widget. Possible Values:"map-only"|"a3-landscape"|"a3-portrait"|"a4-landscape"|"a4-portrait"|"letter-ansi-a-landscape"|"letter-ansi-a-portrait"|"tabloid-ansi-b-landscape"|"tabloid-ansi-b-portrait" 

21. arcgisPrintCopyrightText - Default “Copyright” text in the Print Widget

22. arcgisPrintDpi - Default “DPI” in the Print Widget

23. arcgisPrintFormat - Default “File format” in the Print Widget. Possible Values:"pdf"|"png32"|"png8"|"jpg"|"gif"|"eps"|"svg"|"svgz"

24. arcgisPortalRestAPI - Portal URL for calling the REST API to add zipped shapefile to the map.

25. arcgisGeometryServiceUrl - The link to a Geometry Service which performs geometric calculations such as reshape.  As the ESRI Help indicates, “By default, the geometry service is not started after you create an ArcGIS Server site. Before you can use the geometry service to do geometric calculations, you'll need to start it in Manager or ArcMap.”

26. mapPublishDetails - define "name" of the map template, "value": a short form of the map name,"icon" : assign the icon (image path) , "contextId": context ID,"datagroupId", and “arcgisPrintServer” : the printservice url (This url is the one that is published as map template).

Example:- 

"mapPublishDetails": [ {

  "name" Label shows on the map publishing table of contents, eg) : "Tract Timber Sale Map"-

"contextId": Context ID used for template eg) 315,

"datagroupId": Context DataGroup ID used in template eg) 10,

"layoutName": Layout name eg) "TimberSales",

 "printFormat": Print format eg) "pdf",

 "printDPI": Resolution in dots per inch. Default value is 96. If the dpi value is modified, then the width and height will be modified proportional to the dpi change. eg) 300

"arcgisPrintServer":  Print Server published URL "https:/domain.com/server/rest/services/CF_BRONZE_MAPTEMPLATE/TS_MapTemplate/GPServer/Export%20Web%20Map/execute",

    }

27. spatialEditConfig - As the name describes, this setting is important to have to activate Spatial Edit Buttons (Split and Merge) for the context listed in this setting. 

Example:- 

spatialEditConfig" :[{

    "contextId": 407,

    "contextName" : "Stand"

  }]

28. LRM_ManagedLayers :- This is the most important configuration for running spatial side to work with different modules. This settings will update the map view through the different modules. 

 { "DataGroup": Module ID. It is needed to load layers,

      "managedLayerURL": Feature service URL,

      "mapLayerUrl": Map service URL (THIS is needed for Select TOC functionality)

      "managedLayerCount": Numbers of layer published,

      "geoprocessingLayerURL":GeoProcessing Service,

      "geoprocessingLayerCount": Count of GP services

    }

Example:-  

"LRM_ManagedLayers": [

    { "DataGroup": 10,

      "managedLayerURL": "https://cfflrm-qa-portal.forestry.trimble.com/server/rest/services/CF_BRONZE/Stand/featureserver/",

      "mapLayerUrl": "https://cfflrm-qa-portal.forestry.trimble.com/server/rest/services/CF_BRONZE/Stand/mapserver/",

      "managedLayerCount": "11",

      "geoprocessingLayerURL": "https://cfflrm-qa-portal.forestry.trimble.com/server/rest/services/CF_BRONZE/Stand/featureserver/",

      "geoprocessingLayerCount": "4"

    },

    { "DataGroup": 300,

      "managedLayerURL": "https://cfflrm-qa-portal.forestry.trimble.com/server/rest/services/cfflrm-qa-main/Chemical/featureserver/",

       "mapLayerUrl" : “”,

      "managedLayerCount": "6",

      "geoprocessingLayerURL": "",

      "geoprocessingLayerCount": ""

    }

  ]

Notes: 

1. Application Settings will be managed through Web UI in a future release for administrator users.

2. Refer to Publish a Map on how to publish the layers with edit and read-only privileges. 

Deployment Options

The standard and recommended way to access LRM Web is through Trimble’s network (SaaS - Software as a Service). In this case Trimble’s Single Sign-On grants access all Connected Forest’s services in your subscription.

Alternatively, LRM Web can be deployed on premise, in which case the login process uses the same username/password as in LRM Desktop.