Introduction

Introduction

GEO related information can be configured for display on the device. Generally speaking these settings would be undertaken in conjunction with the customers own GEO team who would provide details and advice on available services.

The general concepts used in the configuration of the maps is as follows:

Licensing

All licensing associated with the use of GEO settings in MyPM is the responsibility of the customer.

Important

  • The URL used (base maps and feature layers) must be https to ensure that its not mixed mode with the MyPM address (which should be https) on browsers
  • The URL domain address (base maps and feature layers) must be added to the white list of addresses of MyPM application build (orgin and content security policy)

If your map service does not have a https option then consider using your SAP Web Dispatcher as an address router. Even with https availability this is could be a good security principal to apply so long as it doesn’t have a performance issue or for use where the map service is not available outside of the companies network.

Configuration Access

To turn on the use of Map functionality in MyPM enable the master setting under ‘Maintain core settings’ from the MyPM Configuration Console:

The ‘Use Google Map’ setting is now Deprecated. The Google Map URL must be maintained for MyPM Admin use with maps and using the customers own Google Map API key as detailed in the Core Settings documentation.

Access the GEO settings from the Maintain Maps Settings tile on the MyPM Configuration Console:

Maintain Base Maps

These are the maps that are displayed, one at a time, on the screen. This is the master list of base maps, they are individually allocated to map profiles which are then assigned to MyPM users.

Configuration Fields

The following is a definition of the configuration fields:

Base Map ID Externally assigned Unique ID for the map
Description Description for the Map
Sort Order Display sort order
Base Map URL The URL for the map tile source. At this stage this is limited to ESRI and Google.

  • ESRI – The address in general will be your own ESRI map service or an agreed base map source
  • Google – The address field refers to the Google Map type rather then a URL. See Google Map Types
Base Map Type The word ESRI or GOOGLE
Can Download Switch on if you wish for this map type to be downloaded. This is only available for ESRI maps and not for Google Map (technically and under Googles terms and conditions, they can not be downloaded)

Base Map Examples

The following are some examples:

Maintain Feature Layers

The feature layers to be maintained in this setting are those coming from GEO services – i.e. ESRI. The layer information for MyPM objects is inbuilt.

Configuration Fields

The following is a definition of the configuration fields:

Layer Externally assigned Unique ID for the Feature Layer
Description Description for the Feature Layer
Feature Layer URL The URL for the map tile source. At this stage this is limited to ESRI
Min Zoom The minimal zoom level at which this layer will be visible where selected. Note that the map service itself can control this setting and the maximum returned number of features
Max Zoom The maximum zoom level at which this layer will be visible where selected. Note that the map service itself can control this setting and the maximum returned number of features
Opacity Control the opacity of geometric polygons for feature areas so that they don’t obliterate the underlying map of other feature layers. Examples: 1 = solid, .5 = 50% opacity
Downloadable Control whether this feature layer will be downloaded for offline reference. Only set on where absolutely necessary
Hide Label Set on to hide the Feature Layers defined label. This can be used where labels overwhelm the display and offer no value to their interpretation
Fields Access and Edit the Fields for the Feature Layer. See next section for details [Requiremed]

Feature Layer Examples

Feature Layer Fields

This configuration is where you specify the pop-up information displayed when you select a feature layer item. These fields are defined in the ESRI settings and may contain a large number of fields that are not relevant to display to a user:

Layer Externally assigned Unique ID for the Feature Layer
Seq Number The field display order in the pop-up
Detail Field Name CS The service description for the field
Detailed Field Label The label to be displayed in the pop-up
Display Field Display this field in the pop-up
HTTP Switch on to display the value of this field as a URL
Call Back Link Create a button to call back MyPM and open this objects record. See related settings below
HTTP Link Prefix Optional maintained with HTTP fields to provide the domain prefix address where not fully provided by the field source.

For example you might have a Share Point site in which you store photos for an Equipment by its SAP Equipment ID. The HTTP prefix might then be something like this:

https://sharepoint.yourcompany.com/photos?equipment=

You would use this on a field with the equipment value and its value would be appended to the URL.

Callback Link Data Used in conjunction with the activation of the Call Back Link above. Used where the map service has an Equipment or Functional Location reference. Single results will open a dialog with the SAP object reference, multiple results will return a list to select from.

The reference SAP Technical objects are limited to:

OBJECT: "EQUI" - for Equipment
OBJECT: "FLOC" - for Functional Locations

The reference fields are limited to:

HTML
Equipment: DISP_ID, TECHID, EQUIPMENT, READ_OBJNR, TPLNR
Functional Location: READ_OBJNR, STRNO, TPLNR

Examples

1. You have a your legacy asset id stored in your GIS system in the field ‘ASSETID’. You have loaded this into SAP in the Technical ID field of the Equipment. The callback parameters you would maintain are:

OBJECT: "EQUI", TECHID: "{ASSETID}"

2. You have maintained your SAP Equipment ID your GIS system in the field ‘EQUIPMENT’. The callback parameters you would maintain are:

HTML
OBJECT: "EQUI", EQUIPMENT: "{EQUIPMENT}"

3. Tour have maintained your SAP FL Label Field in your GIS System in the Field ‘SAPFL’. The callback parameters you would maintain are:

HTML
OBJECT: "FLOC", STRNO: "{SAPFL}"

Here’s a example of the configuration of fields for the Department of Conservation NZ Great Walks, the the resulting popup:

Layer Groups

Use this to build a tree menu for display of the Layers. Typically these would mimic the layering used in the GEO system, however given the display space available rationalisation may be necessary:

Group No Externally assigned reference
Parent Group The Group No of the parent. Use 0 is level 0
Level The level, starting at 0 for this object
Description Display description
Sort Sort Order within the Parent Group or top level
Layer Links Navigate to the Layer Links tab and apply a filter for this Layer

Example:

001    0       Animals   1 Animals
Cats
Dogs
Fish
Snapper
002    0       Fish         2
003    001   Cats        1
004    001   Dogs       2
010    002   Snapper  1

Layers to Groups

This is where you assign the configured Feature Layers with the Layer Groups. Its considered self explanatory and here’s an example:

Profiles

Configuration of base maps and layers is controlled at the MyPM user level through the assignment of Map Profiles in their MyPM profile/s. Its set up is considered self explanatory, here’s an example:

Profile Layers

The Profile layers are assigned to the Profiles via this configuration. Its set up is considered self explanatory, here’s an example:

Profile Base Maps

The Base maps available for use are assigned to the Profiles via this configuration. Its set up is considered self explanatory, here’s an example:

Defaults

This is where the default settings are maintained for the GEO functionality:

Setting Explanation Recommended Setting
Default Base Map The default online Base Map to Display – this should be in all Profiles
Default Offline Base Map The default offline Base Map to Display – this should be in all Profiles
Google API Key The Google API Key for your organisation – if Google Maps is used
Default Zoom The default zoom level that maps are displayed at 16
Max Download Zoom The download zoom level from which offline Map tiles and layer data should apply 19
Work Download Radius For layers that are offline and for applicable MyPM Work Order Objects this is the radius in meters that will be downloaded 0200
Screen Download Radius Where users elect to download specific points in anticpation of going offline, this is a radius around the selected point that will be downloaded 0500
Max Tile Age This is the age, in days, after which downloaded map tiles, that have not been accessed, will be deleted 30