GIS 2.0 Features many configuration enhancements over its predecessor. The hierarchy now has infinite depth with every level able to be represented on the map. More map providers are supported along with the ability to load pre-rendered map files from disk. A richer user interface simplifies the configuration of alarming, custom icons, area pins and dynamic positional updates a great deal.
We have also updated the feature set to support static graphics via shapefiles and KML files. Zoom level based pin visibility makes it easier to provide different information depending on detail levels. Configurable tooltips allow the user to show live data when hovering on the pin. The treeview has been included natively in the control to allow better search and filter capabilities. The alarms are also indicated on the tree, with the option to drive the selected pin information to any other form components using spiders.
Bulk configuration of GIS 2.0 can still be accomplished in excel. Importing of legacy GIS 1.0 configurations is also possible if a valid legacy excel sheet is available.
The GIS 2.0 requires SmartUI 10/MAPS 4 or later and will be made available as part of the Addition Components Install.
The GIS datasource is now added directly on the Datasources node in the Enterprise Manager tree. The following options are available on the datasource:
Save: Saves the GIS datasource configuration to an XML file in [configuration path]\GIS.
Add: Presents the UI to add a new child node
Import/Export: To make sure a valid format is used, start by making a few nodes in the datasource from first principles. Then save the datasource and export the configuration. This will provide you with a good example of how to complete the cells. Importing completely overwrites the current configuration (no merge!).
Connection Details: Since GIS is now a licensed component, some demo nodes are provided. This dialogue shows how many nodes are in use/licenced. When licensed, there is basically no limit on the amount of nodes that can be added.
When a new node is added the only strictly required field is a unique name. Options are provided to set the node location statically or to select tag values that will drive the location dynamically. Position data should be provided in decimal representation. The zoom levels, colour and icons are inherited from the parent to allow for quicker default configuration. Setting the default zoom level to -1 will make the node permanently invisible on the map (hierarchy only node). The attributes are free text, key-value pairs for filtering and searching purposes.
A pin can be configured to be represented by an area. An area pin is a free form polygon, described by a collection of latitude longitude combinations. Alarming and selection is displayed like in pins, however, the status colour will fill the entire region. Region colours are applied with a lower opacity as to not obscure any pin items beneath it completely. Area pins cannot be driven dynamically.
There are tabs for configuring opening of graphic forms from the pin, alarming and status indication on the pin and pin tooltips.
The map control should be available in the toolbox under GIS, after the component is installed. The key properties to set are the datasource and map provider properties. OpenStreetMaps is an open source provider and Bing Maps requires a valid Bing maps key. LocalMaps are pre-rendered tiles that can be provided for a certain area on request and are ideal for fully offline systems. The map will only be visible in run mode or in the operator.
Pins are added to the map for all the nodes in the datasource. Map pins are drawn on the map surface at the required latitude and longitude. Each pin can indicate selection, status and alarm. The selected state is indicated by a bold border. If alarmed, the pin border will turn red. The lower triangle of the pin will be in the configured status colour (defaults to pin colour). The main pin real estate can contain a custom icon.
The treeview displays the nodes in a hierarchical context. It has a filter bar that allows the user to show only pins matching the terms provided. Users can filter by name, attributes, alarm state and descriptors.
Pins that are invisible by zoom level will all appear in (and be filtered by) the treeview, but are coloured light grey. Alarm states are also represented in the tree. A red square indicates that an item is in alarm. A red rectangle indicates that the item has a child that is in alarm. Both states can be visible simultaneously.
The map control supports loading of custom shapes as static items. Shape data can be loaded from shapefiles (.shp + .dbf) and Keyhole Markup Language files (.kml). Each shape file is loaded onto its own user map layer. This allows the layers to be ordered and turned on/off on demand. Shapes in these files have configurable background and selected colours. The user can also set at which zoom levels the layer should be visible