Select Dataset

M.App Studio Help

HGD_Product
M.App Studio
HGD_Portfolio_Suite
M.App Tools

In Select Dataset modal window select geometry and/or attributes for the BI. Depending on your datasets, attributes may be provided within geometry database or separately. Both geometries and attributes can be picked either from those available in the storage (added by you or shared with you by others) as well as data can be fetched from an external secure data source over HTTPS.

Select Dataset from Content

To add a dataset (geometries or attributes) from content pause on a selected (in Dataset From Content box) dataset you want to add. The thumbnail for the data displays. Click + (Add) button. Selected datasets appear under selected geometries and/or selected attributes respectively. For more information about content management control see: Content Manger.

Select Dataset from External Source

To provide an external dataset, type the service URL in the Select Dataset From External Source Field. Next click the Add button.

In order to add external data source for your BI data, provide a secure URL (over HTTPS) pointing to it.The geometry data source should return a valid GeoJSON file with “application/vnd.api+geojson” MIME type and attribute data sources should return a valid CSV file with “text/csv” MIME type. Also, the external server should have proper Access-Control-Allow-Origin header in order to allow such connections. In particular, the external data sources can point to WFS GetFeature requests only if the WFS supports "application/vnd.api+geojson" and "text/csv" output formats. You can easily publish such a service by using GeoMedia WebMap 2016 or newer.

Attributes Source Data

Specifying the attributes source is optional if geometry source already contains attributes. When the attribute data source is not selected, then the attributes are built from the geometry (GeoJSON) properties. In such case, each table row is connected to one geometric feature.

light_bulb_iconAll special characters and spaces in CSV and geojson column names are converted into “_” character.

Uploading New Data

Using the Content Management Control and drag&drop method you can also upload data from your local drive or network share. Uploaded data will be added to BI configuration.

Primary Key

Having selected geometries and/or attributes the wizard suggests the Primary Key - an attribute that uniquely identifies geometries. You can select the Primary Key manually. Select the attribute from the dropdown list. The list is populated automatically depending on the already selected dataset.

Combining data from several sources

It is possible to combine several attributive datasets into a single data table for particular Data Stage. In order to combine data sources, just select two or more attribute data files (CSV) and join them by using options under Join Datasets.

Supported Input Data

  • Map Data
    • Base Map – the same maps as used in any Smart M.App. Those maps are generated with Map Editor available in the M.App Studio.
    • Geometries – spatial data in GeoJSON.
  • Attribute Data
    • CSV

Select Dataset dialog:

BIWizard_2_DataSets

light_bulb_iconYou can display multiple geometries (on a Choropleth Map or a Point Cluster Map) and analyze them together in your BI Smart M.App by configuring two or more geometry sources in your Smart M.App. You can define the color palette for each geometry separately. Defining multiple geometries it is possible to compose your BI map and use “geometry generalization” to display only the relevant level of detail. You will see one geometry at a time, but when you zoom in or out then the next/previous geometry displays according to the defined scale range. In addition, if you correlate both geometries (geometry keys) with the tabular data, all selections and filters will smoothly move between the layers and widgets will interact with different geometries. Also, you can filter geometry at any level and when you change the scale/view the filter works for another layer as well. The only thing that is required by the user in the configuration is to assign appropriate key fields to corresponding geometry layers. See Multiple Geometries topic to learn more.