Universal GUI - Maps

Hi Freddy,

Looks like the coordset is not in the correct format. The lat & lon columns in the JSON need start with an upper case; Lon & Lat.

Regarding the base layer not being enable by default, are you up-to-date with all the hotfixes?

Hope this summary of how to implement the Maps component helps.

To show information in the Maps component you need to configure a few steps in Maps screen of the SF.

Step 1. Preparation

Before we begin with the configuration of the map itself, there are some prerequisites for the entity we want to use the maps for:

• The entity needs to contain a column which categorizes the data; the mapping column.
  • This column needs to have a image combo domain.
  • The image of the element are used as the marker on the map
  • You need to have at least one element, more are useful if you have different data inside the entity like a route with a start point, destination and route.
• The entity needs to contain a column with the longitude and latitude coordinates
  • This needs to be save in a specific JSON format: { "CoordSets": [ [ { "Lon": "5.9795099", "Lat": "52.2084904" } ] ] }
  • In case the data should visualize a line (used for routes) or polygon (used for areas) the JSON must contain multiple coordinates in the coordset: {"CoordSets":[[{"Lon":"-76.499107","Lat":"39.243073"},{"Lon":"-76.499146","Lat":"39.243053"}] ] }
  • The coordinates are not automatically retrieved by Thinkwise, so make sure you have a process in place to call an Geolocation webservice from example Google, Here, OpenMaps, Mapquest etc.
• The entity should contain a column with the value you want to show in the popup when an location is selected.
  • This could only be plantext with only the lookuk value of the entity.
  • The popup does support HTML, so you are free to design a rich popup with forexample pictures and table structures.
• The screentype of the entity must include a maps component

Step 2. Configuration of the entity

If the entity meets all requirements you can start with the configuration, open User Interface > Maps, find the right entity and press add.

Start with the basic information; the Linked columns and choose the correct columns.

Of the initial settings, only the Zoom level is mandatory, this should be a value between 1 and 16 and indicates how much the map is zoomed in when it is first opened.

The initial Latitude & Longitude are used to center the map on a location if there is no data in the selection to show on the map. This happens rarely, but can have the following reasons:

• The entity does not contain any data
• A filter has been applied which does not return any data
• The available data has no value for the Data mapping column and/or Latitude and Longitude column

Step 3. Configuring the base layer

Every map needs at least one base layer, because this base layer functions as a representation of our planet. Without a base layer, the locations are shown on a white background.

For the base layers, you can use external providers such as Google, Here maps, Openmaps, Mapquest or your own favourite map provider.

The only requirement is that the map can be accessed using a so-called X,Y,Z url.  The XYZ source is used for tile data that is accessed through URLs that include a zoom level and tile grid x/y coordinates. For example: https://mt0.google.com/vt/lyrs=m&hl=en&x={x}&y={y}&z={z}

Step 4. Setup overlays (Optional)

Overlays is the only optional step. This can be used to add extra information on top of the base layer.

Think of No Fly Zones, Environmental Zones, Traffic Information.

Step 5. Define the data mappings

With the configuration of the data mapping you control how the data from the entity is visualised on the map.

You specify how specific records should be visualised based on the elements of the Data mapping column. It is important to note that the records will only be visualised if the column show data mapping is set to true.

Standard locations are of the Geometric type Marker. For these records the image linked to the element will be shown directly on the map, of course based on the coordinates.

If a record contains data for a route, it will be configured according to the type Line, in which case you have the possibility to specify additional settings like the color.

​​​​