MAP/MARKER/LINE SETTINGS
This topic describes all the dynamic settings of the Data Layer. That means every setting of this dialog is calculated for each dimension record. Condition Coordinates SETTINGS Type (for MARKER and LINE only) Heading (for MARKER only) Style (for LINE only) LineBend (for LINE only) Pattern (for MAP only) Size or Width (for MARKER and LINE only) Size% or Width% (for MARKER and LINE only) BorderColor (for MARKER and MAP only) BorderColor% (for MARKER only) BorderSize (for MARKER and MAP only) BorderSize% (for MARKER only) ImageSize (for MAP only) ImageSize% (for MAP only) ImageOpacity (for MAP only) ImageHeading (for MAP and LINE only) ImagePosition (for LINE only) Metadata - Info and KPI |
The values for nearly all features may be entered as calculated |
For detailed information about notation in this dialogs go to chapter The fx‑editor. |
MAP / MARKER / LINE SETTINGS |
|||
---|---|---|---|
SETTING / VALUES |
EXPLANATION |
||
|
|
||
|
|||
if(1=1, [settings] ) |
Condition for calculating the Layer/record. |
||
|
|
||
Set coordinates for Polygons, Markers or Lines. |
|||
MAP Coordinates Coordinates multiple coordinates |
Polygon Coordinates in WGS84 projection format, using: Encoded Polylines: GeoJSON MultiPoligons (KML): file name (file stored within NPGeoMap extension directory, subfolder "maps"): Access to all NPGeoMap Map files: https://s3.eu-central-1.amazonaws.com/npgeomap/maps |
||
MARKER Coordinates Marker single coordinates |
Coordinates in WGS84 projection format, using: Latitude, Longitude (SinglePoint) GeoJSON Points (KML) MultiPoints |
||
LINE Coordinates Start single coordinates End single coordinates multiple coordinates |
"Start" and "End" of a Line Coordinates in WGS84 projection format for Start and End of Lines, using: Latitude, Longitude (SinglePoint): GeoJSON Points (KML): The system always connects a Marker with a Endmarker, in the order they are loaded - the first coordinates of "Start" with the first coordinates of "End", then the second coordinates of "Start" with the second coordinates of "End", and so on. Therefore, if you want to create a one-to-many connection (or many-to-one), just set the same coordinates in "Start" (or "End"). If there is not the same number of coordinate points in "Start" and "End", the surplus coordinates are displayed as simple points. Path Coordinates Path Coordinates in WGS84 projection format (3 or more points in a row), using: Latitude, Longitude (separated with comma and semicolon): Latitude, Longitude (separated with space and pipe): GeoJSON MultiPoints (KML): Encoded Polylines: file name (file stored within NPGeoMap extension directory, subfolder "maps"): Several Path sections are separated by hash "#".
|
||
|
|
||
In this section there are all features for setting functionality and presentation (Labels, PopUps, MouseOvers/Tooltips,...) of Markers. |
|||
Type number
|
MARKER SETTINGS: Set the Marker type/shape in which Markers are displayed: 0 = don't show Markers 1 = don't show Markers, but the Label 2 = circle (default) 3 = triangle 4 = square 5 = pentagon 6 = hexagon 7 = Heatpoint for Heatmaps You can also display an Image or a small ImageChart INSTEAD of a shape - settings further below. LINE SETTINGS: Line types: 0 = no Line A GreatCircle is the geographically shortest connection between two points. Due to perspective distortion (because of projecting the 3D globe on a 2D map), this line may look like a curve, depending on the position and the projection type. Nonetheless it is the correct course. Therefore this Line type is best for displaying airlines and flight routes. Curved Lines are a visual alternative to straight lines. In some cases they may look better than straight Lines. The Line type Beatle is for instance best for displaying global interaction and cash flow. Swing Lines are a good choice to connect for instance Customers and Branches. Bending Lines are the most flexible ones, as their bending angle can be freely adjusted - see setting "LineBend". |
||
GreatCircles: type = 2 |
Curved Lines: |
|
|
Beatle Lines: type = 4 |
Swing Lines: type = 5 |
Bending Lines: type = 6 |
|
Heading number |
Marker heading 0-360 (degrees), |
||
Style parameter |
Line/Path style: solid dot dash dashdot longdash longdashdot
|
||
LineBend number |
This feature can only be used with Line Type 6 - Bending Lines. |
||
color |
Marker fill color. When setting colors you can use Hex-Codes, HTML color names or RGB |
||
number |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. |
||
Pattern parameters |
Polygon fill pattern Parameters (all separated by pipe"|"): pattern type (line, dot, circle, tile, square - or one from the list below) color (or "false" for using Polygon color) opacity (0-100 percent) size (px) spacing (px) angle (0-180 degrees) Patterns with a fixed size: *In most cases this character is somewhere in the third level of the keyboard, available by pressing Alt Gr . |
||
number |
Opacity of the fill color in percent: 0% - colors are covering |
||
Size number LINE SETTINGS: Width number |
MARKER SETTINGS: Radius of Markers or Images. LINE SETTINGS: Line width in pixels. |
||
Size% number LINE SETTINGS: Width number |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. |
||
BorderColor color |
Border color of Polygons or Markers. When setting colors you can use Hex-Codes, HTML color names or RGB |
||
BorderColor% number |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. |
||
BorderSize number |
Border size/width in pixels. |
||
BorderSize% number |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. |
||
content |
Set Labels for Polygons, Markers or Lines. |
||
parameter |
Label position, relativ to the object center. |
||
Parameters: tl = top left tr = top right bl = bottom left br = bottom right cl = center left cr = center right ct = center top cb = center bottom cc = center center |
|||
content |
Tooltip (or mouseover) for Polygons, Markers or Lines. |
||
Use Qlik variables, fields and formulas for dynamic content. Example: & '#Tooltip=' & 'Hello World'
Important: If you want to use local image files in HTML, you have to indicate the following Qlik image path: Qlik Sense: ../Extensions/NPGeoMapSense_v3/images/[...] Example with image: & '#Tooltip=' & '<div style="text-align:center; background:#F0F0F0; padding:5px; border: 5px solid gray;border-radius:10px "> content <br> QlikView: /QvAjaxZfc/QvsViewClient.aspx?public=only&name=Extensions/NPGeoMap_v3/NPGeoMap_v3_Basic/images/[...] Example with image: & '#Tooltip=' & '<div style="text-align:center; background:#F0F0F0; padding:5px; border: 5px solid gray;border-radius:10px "> content <br> You can copy-paste this example to try it yourself! You can use several NPGeoMap [#Hashtag] variables in here: Example: & '#Tooltip=' & 'Sales: [#KPIsales]' More information about integrating Qlik fields or formulas and further details on notation see chapter fx-editor. |
|||
content |
A PopUp is a kind of dialog or a small window, that opens or "pops up" if you click on a dynamic object (Polygon, Marker, Line). NPGeoMap can display text and dynamic content in a PopUp. |
||
Important: If you want to use local image files in HTML, you have to indicate the following Qlik image path: Qlik Sense: ../Extensions/NPGeoMapSense_v3/images/[...] Example with image: & '#Popup=' & '<div style="text-align:center; background:#F0F0F0; padding:5px; border: 5px solid gray;border-radius:10px "> content <br> QlikView: /QvAjaxZfc/QvsViewClient.aspx?public=only&name=Extensions/NPGeoMap_v3/NPGeoMap_v3_Basic/images/[...] Example with image: & '#Popup=' & '<div style="text-align:center; background:#F0F0F0; padding:5px; border: 5px solid gray;border-radius:10px "> content <br> You can copy-paste this example to try it yourself!! You can use several NPGeoMap [#Hashtag] variables in here: Example: & '#Popup=' & 'Sales: [#KPIsales]' The following NPGeoMap #Hashtag Variables are provided, for additional information about the coordinates: [#Latitude] (WGS84 Latitude coordinate) [#Longitude] (WGS84 Longitude coordinate) [#PRJ=EPSG:xxx] (converts the variables above by provided EPSG Code) Example: simple: converted: integrating GoogleMaps Streetview:
More information about integrating Qlik fields or formulas and further details on notation see chapter fx-editor. |
|||
Qlik object ID |
Feature for displaying any Qlik visualizations in a PopUp. QlikView: Qlik Sense: |
||
file path or SVG |
Set Image. Example (file in folder "image"): & '#Image=' & 'flag.png' Example (file in sub folder "demo"): & '#Image=' & 'demo/airplane.png' Example (screenshot): & '#Image=' & 'office_11.png' You can copy-paste the examples to try it yourself! Tip: It's possible to use animated GIFs. SVG images: <svg width="30" height="30" xmlns="http://www.w3.org/2000/svg" version="1.1"> Just replace width and height by your needed sizes and add svg components like: circles, polygons, text... |
image file:
SVG image: |
|
It is important to include the "xmlns" attribute, "width" and "height" and optionally in addition the "version". Example circle: & '#Image=' & '<svg width="30" height="30" xmlns="http://www.w3.org/2000/svg" version="1.1"> Example polygon: & '#Image=' & '<svg width="30" height="30" xmlns="http://www.w3.org/2000/svg" version="1.1"> Example with dynamic content (screenshot): & '#Image=' & '<svg width="130" height="130" xmlns="http://www.w3.org/2000/svg" version="1.1"> You can copy-paste this example to try it yourself - just replace the Qlik field "Capital" by a existing one. |
|||
content |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. |
||
Type number Data number BorderSize number BorderColor color Color color Label text |
Instead of an Image, an Image Chart can be displayed. "Type" 0 = no Chart 1 = Pie 2 = Doughnut 3 = Bar |
example for |
|
"Data" The data has to be separated by a vertical bar/pipe character* | . Concat(Aggr(sum(Sales),ID, Month),'|',Month) Concat(DISTINCT Month, '|', Month) "BorderSize" and "BorderColor" If you don't fill anything in here or remark the line, no border will be displayed. "Color" If you don't fill anything in here or remark the line, the ImageChart will be displayed in default colors. When there is more data set than colors in this feature, first it goes on with the default colors and then they all will be repeated. When setting colors you can use Hex-Codes, HTML color names or RGB "Label" The labels have to be separated by a vertical bar/pipe character* | . If you edit anything in this section, make sure to enable the line "& '#ImageChart='" as well, in order to let the system know where you are working. |
|||
ImageSize content
|
Image size in pixels. To set the size of Images for MARKERS and LINES, use the setting "Size"/"Width". |
||
ImageSize% content |
Set here a KPI or other number values (for example Sum(Sales)) instead of a color/size/image value, to determine the colors/sizes/images with Classes. To set the size Class of Images for MARKERS and LINES, use the setting "Size%"/"Width%". |
||
ImageOpacity content |
Opacity of the fill color in percent: 0% - colors are covering |
||
ImageHeading content |
Image heading 0-360 (degrees), |
||
ImagePosition content |
Set position of the image along the Line: 1 = start/beginning of Line 2 = center 3 = end of Line |
||
|
|
||
|
|||
Info text KPI number |
Set metadata here, to use it for example in Tooltips or Popups. "Info": "KPI": & '#KPIsales=' & sum(Sales) & '#KPIprofit=' & sum(Profit) Always start with a hash "#" and "KPI" and add a custom name. & '#Popup=' & 'Sales: [#KPIsales]'
*Use the following NPGeoMap [#Hashtag] variables to display the content elsewhere: [#KPI] - cumulative KPI amount (as well as all your custom KPI variables, e.g. [#KPIyourname]) Those variables can be used inside Tooltip and Popup of this dialog |