MAP

MAP is a visual user control used to add a map area directly to a SCADA screen design. An examination of the source code shows that the map request is constructed by combining the control's dimensions, center coordinates, map type, the appearance of specific map elements, visibility settings, zoom level, detail, brightness, and saturation.

For this reason, the MAP control differs from a conventional data indicator. Instead of displaying a pointer, LED, bar, or numerical value, it presents a geographical image as a visual component of the SCADA page. The map center and visual details can be reconfigured through its properties.

The provided ProcessEkstraParamVals code clearly demonstrates the relationship between the MAP control's properties and the map request. The control dimensions, center coordinates, map type, and style/visibility parameters are sequentially appended to MAPCOMMANDCALLSTR.

The source code calls the GETBINGMAP() method in the final step. Since the method body is not included in the provided code excerpt, the details of the underlying mechanism used to download or display the image have not been assumed on this page.

Control Size → Center → Map Type → Elements → Visibility → Zoom → Scale → Brightness → Saturation → GETBINGMAP()

In the source code, the query portion of the map URL is constructed step by step in the MAPCOMMANDCALLSTR variable. Initially, the image dimensions are determined using the control's actual width and height. The center, map type, element styles, visibility settings, and image parameters are then added.

String mapstr = "http://maps.BINGapis.com/maps/api/staticmap?"
             + MAPCOMMANDCALLSTR
             + "&sensor=false";

As this structure shows, the MAP control is designed to retrieve the map image through a static map request. Since the URL query parameters are generated from the control properties, the same MAP control can be reused with different coordinates and display settings.

The Latitude and Longitude properties determine the geographical point at which the map is centered. In the source code, these two values are converted directly into the center parameter.

MapType is the property that determines the map's basic visual type. Its default value in the source code is defined as Roadmap. Since the source does not provide all the options of the GNHaritaTuru type, this page describes only the verifiable default value.

The map type should be considered together with the other visual properties. A road-focused view and a more visual or satellite-based view may present different levels of information density on the operator screen.

One notable feature of the MAP control is its ability to handle different map elements separately. The source code creates both element style and visibility parameters for six elements: roads, landscape, administrative features, POI, transit, and water.

In the source code, these properties are converted into query fragments in the form style=feature:.... This makes it possible to determine which visual elements affect the different components of the map image.

The visibility of map elements is managed through separate properties in the MAP control. An examination of the defaults in the source code shows that Off is used for roads, landscape, administrative features, POI, and transit, while On is used for water.

In addition to the basic location and element settings, the map has four important display parameters: Map Zoom Factor, Map Detail Factor, Map Brightness, and Map Saturation. The source code adds all these values directly to the map request.

In the source code, the map image dimensions are not assigned fixed values. Instead, they are obtained through MyWebBrowser.Width and MyWebBrowser.Height. This allows the request's size parameter to be generated according to the control's actual on-screen dimensions.

UpdateInterval is used to control the update timing. The code attempts to convert the value to an integer, falls back to 1000 if the value is invalid, and also prevents the update interval from dropping below the minimum permitted by the system. The timer interval is then set to this value.

The provided ProcessEkstraParamVals method does more than read visual properties; it also reveals the MAP control's operational workflow.

1. Parameters from older versions are checked and updated if necessary.
2. If DecimalPoint is missing, the default value 0 is added.
3. The parameter text is converted into a dictionary, and the user control name is updated.
4. Action Event information is retrieved.
5. Background, foreground, and font properties are applied.
6. The map dimensions are obtained from the control's width and height.
7. The center is defined using Latitude + Longitude.
8. MapType is added.
9. Style components are added for the six map elements.
10. Visibility settings are added for the six map elements.
11. Zoom, detail, brightness, and saturation parameters are added.
12. The update interval is validated and applied to the timer.
13. Authorization level and group information are read.
14. The map is retrieved by calling GETBINGMAP().
15. Bound data updates and parameter storage operations are performed.

The MAP control can be considered for applications where displaying a map as part of a process screen is useful. It can be used to create a map area in designs where the geographical location of a site, facility, station, distribution point, or other location must be presented visually on the operator screen.

The strength of the MAP control lies in the ability to reconfigure the same basic control for different screen purposes. The following examples illustrate how the properties in the source code can be considered together.

The complete option lists for the GNHaritaTuru, GNHaritaBilesen, and GNGorunurlukTuru types used in the source code are not included in the provided material. Therefore, only the values explicitly visible in the source are documented below.

The main properties defined in the MAP control's source code are listed below. Default values are taken directly from the provided C# definitions, while the Turkish equivalents are based on the mappings in the current terminology dictionary.

Current technical documentation for map services indicates that static map requests can be configured using parameters such as center location, zoom, image type, image size, and visual style. Managing map element visibility and styling through separate rules is also consistent with the general static map approach.

The address in the provided source code has the form http://maps.BINGapis.com/maps/api/staticmap? and generates parameters such as size, center, maptype, style, zoom, and scale. Since current service documentation may use different endpoints and API models, it is important to verify the service address used in the application's actual operating environment.

• Static Map Technical Documentation

MAP is a user control designed to add a geographical display area to SCADA screens, with an appearance that can be extensively configured through its properties. The center location is defined by Latitude and Longitude, while Map Type, map elements, visibility, zoom, detail, brightness, and saturation settings determine how the image is presented.

One of the most important aspects of the source code is that these properties are not used independently; instead, they are combined as components of a single map request. This makes MAP a configurable map area whose center and visual details can be adjusted to suit the SCADA screen design.