Maintain Map Default Settings

This is where the default settings are maintained for the geospatial map functionality:

Settings

FieldDescription/ UsageRecommended Setting
Default Settings
Default Base MapThe default online Base Map to Display - this should be in all Profiles
Offline Base MapThe default offline Base Map to Display - this should be in all Profiles
Google API KeyThe Google API Key for your organisation - if Google Maps is used.

Value:
"https://maps.googleapis.com/maps/api/js?key=" & key

So if your google map api key was '123' input:
https://maps.googleapis.com/maps/api/js?key=123
Note that this field, as of SP11, has a password mask applied to protect it from being inadvertently exposed. A password mask also stops the value from being copied. If you need to see the value maintained, export the config setting and review in the BlueWorx Map Defaults csv file.
Default ZoomThe default zoom level that maps are displayed at16
Max Download ZoomThe download zoom level from which offline Map tiles and layer data should apply16
Max Display ZoomThe lowest level that a user can zoom to - depends on your map server settings
Work Download RadiusFor layers that are offline and for applicable BlueWorx Work Order Objects this is the radius in meters that will be downloaded.

Important: Setting this value to greater than 200 meters can dramatically increase the sync time and data volumes on the device, proportional to the work order objects with spatial references and geo-layers marked as offline.		200 (meters)

Screen Download RadiusWhere users elect to download specific points in anticipation of going offline, this is a radius around the selected point that will be downloaded

Important: Setting this value to greater than 500 meters can dramatically increase the sync time and data volumes on the device, proportional to the geo-layers marked as offline.		500 (meters)

Max Tile AgeThis is the age, in days, after which they were downloaded will be deleted.

In setting this value consider:
  • Is the map data for general use relatively static for your users and changes infrequently? In which case set to 0
  • For service industries, whose workers may range over distances, set high enough that you're not needlessly re-downloading common use map data and low enough that you don't fill the device database


Max Tile Zoom for Persisted Map FeaturesThis is the maximum zoom level at which all BlueWorx map features (i.e. Locations, Annotation, and Actions) are resolved to. i.e. we start locating features on map tiles at this level and continue to move to lower levels until we can fit the feature on one map tile. For example, we start at 14, and then, if an object doesn't fit cleanly in a single map tile, we move to 13 and so on.

In setting this value consider:
  • If you set anything below 10 (i.e. 9), the maps are going to be unusable. That's because too many objects will be retrieved when searching, even though they may not be seen on the visible portion of the map - i.e. you're trying to resolve asset locations at a Country/ State/ Large Region
  • You could set higher (i.e. 12,13,14) if you have lower feature density for the majority of your common assets - for example, transmission pylons and lines. The impact of higher settings is better performance when accessing the map or searching spatially in SAP. However if what you're trying to see exceeds the maximum, then you may not see the feature
  • You could set lower (i.e. 15,16,17) if you have higher feature density for the majority of your common assets - for example, power poles. The impact of lower settings is poorer performance when accessing the map or searching spatially in SAP 
  • This is not the value at which a feature is displayed. That's a different and independent to each feature setting

If you change the value, you will need to run the program /SOLTIUS/EM_RF_FEATURE_TILE to adjust the map tiles.


Between 12 and 17

SAP Search
Max Layer ReadWhen spatially searching SAP (online) we will only read selected features up to this many layers (in the layer selection multi-select field).

If you set this too high, then performance may make the feature unusable.		2 or 3
Max Result ReadWhen searching SAP, at each zoom level, we read for the bounds of the map (that is from the top left to the bottom right corners). If the number of features contained within this bound are found, then we will not retrieve/ display them.

If you set this too high then performance may make the feature unusable and (for online searches) SAP performance could be impacted. If you set this too low then you run the risk of not seeing all you features.

Optimise through trial and error. Setting will depend on your SAP performance and the density of assets. To test pick an area with a high concentration of assets and note that over time in production this figure may need adjustment if you add additional features/ collect more data.		10,000