Metadata can be associated with spatial data sources in JMap. It can include information such as the person who produced the data, the date it was updated, a description, etc. Users can view this information for the corresponding layers in JMap applications. Metadata can be entered directly into JMap Admin using preset templates or it can be taken from an external metadata management system. Refer to the Metadata Templates section for more information on creating templates.
To access the metadata settings of a spatial data source, click on Metadata in the details section of a spatial data source. The following options are available:
Layers whose data originates from spatial data sources with metadata will automatically inherit this metadata. Metadata can be viewed by users of JMap Web, JMap NG and JMap Pro applications.
External attributes for a spatial data source are attributes that are obtained from an external database (external means a database that is separate from the data source itself). The external attributes are added to the list of existing attributes and can thereafter be used like any other attribute in reports, queries, mouseover, thematics, etc.
External attributes are available only for vector spatial data sources that read data from files (shp, mif, tab, dwg, dgn, etc.) and JMap Spatial tables. When working with vector data sources that access data inside existing spatial databases (PostGIS, MySQL Spatial, Oracle Spatial/Locator, etc.), this option is not available. In that case however, it is often easy to include all needed attributes using normal SQL joins with other tables or by creating views.
External attributes are created from the spatial data source creation wizard.
To create an external attribute, choose External attributes in the Attribute section of the wizard. Press Add and choose one of the following two methods: Select fields or SQL query.
Choose this option in order to select one or more fields from a specific database table from which you want to obtain the values. This option is the simplest method, and it allows you to create several attributes at once.
Choose this option to provide an SQL query that will extract the attribute values in the database. This method is more flexible, but limits you to creating one attribute at a time.
The spatial data source (SDS) configuration interface allows you to access information on a source as well as parameter configuration functions such as metadata, permissions, and attributes.
The attribute configuration window contains two tabs: Metadata and Attribute sample.
The Attribute sample tab displays the value of the attribute for a sample of SDS elements.
In the case of raster SDS created from the GDAL library, the configuration interface allows you to add reference coordinate systems to the original projection system of the data. The section provides details on this topic.
This button in the Attributes section allows you to update the SDS statistics.
Type
3 options are possible: None: No metadata is associated with this data source. External: The metadata comes from a metadata management system that is outside of JMap and accessed through a URL. The URL must be entered in the URL field below. Template: The metadata is entered directly in this section using the selected template.
URL
If the type of metadata is external, this setting defines the URL to be opened in order to view the metadata associated with this spatial data source.
Template
If the type of metadata is template, select the template to be used for this data source.
The metadata entry form for this template displays.
Enter the metadata in the various fields.
Database
Select the database from which the attribute values will be taken.
This database must already be configured in JMap Admin.
Schema
Select the schema containing the table.
Table
Select the table containing the fields to be used as external attributes.
Include
The list of available fields is displayed.
Select the ones to be included as external attributes.
Get value from
Indicate the name of the field.
Attribute name
You can give the external attribute a name that will be different from the field name.
Dynamic attribute
Select this option if you want the attribute to be dynamic.
Dynamic attributes are read directly from the source in a dynamic manner.
Attributes that are not dynamic are imported into JMap’s system database and are only reread when the data source is updated.
In certain cases, dynamic attributes can reduce the system’s performance.
Join on fields
Select the parameters of the join between the external data and the JMap data source.
Aggregation type
This option is only available if a single field is selected.
Select the aggregation method to use if more than one value is found for the same geometry: Keep first element: Keep only the first value found. Average: Calculate the average value to use as the attribute value. Only available for numeric attributes. Summation: Calculate the summation value to use as the attribute value. Only available for numeric attributes. Using separator: Build a string containing all values separated by the specified character. Only available for text attributes.
Attribute name
Enter a name for the external attribute.
Dynamic attribute
Select this option to make the attribute dynamic.
Dynamic attributes are read directly from the source in a dynamic manner.
Non dynamic attributes are imported in JMap’s System database and are only reread when the spatial data source is updated in JMap Admin.
Dynamic attributes can impact performances in some situations.
Database
Select the database from which the attribute values will be taken.
This database must already be configured in JMap Admin.
SQL query
Enter the SQL query to be executed in the external database that returns the values to use for the external attribute, along with the field used to join with the data source.
Press Execute to test the query and to initialize the other parts of the interface.
Get value from
Select the table and the field to get the values from.
Only those returned by the SQL query are available.
Join on fields
Select the parameters of the join between the external data and the JMap data source.
Aggregation type
Select the aggregation method to use if more than one value is found for the same geometry: Keep first element: Keep only the first value found. Average: Calculate the average value to use as the attribute value. Only available for numeric attributes. Summation: Calculate the summation value to use as the attribute value. Only available for numeric attributes. Using separator: Build a string containing all values separated by the specified character. Only available for text attributes.
Metadata |
|
Type | Indicates the attribute’s data type. |
Dynamic | Indicates whether the attribute is dynamic. |
SQL Type | Indicates the SQL type of the attribute data. |
Indexed | Check this box to have the attribute indexed. |
Title | You can change the title of the attribute. |
Format pattern | Specify a format pattern for displaying SDS items. The pattern must follow the Java standards. |
Upon saving, recursively apply to associated layers… | By checking the appropriate boxes, you will apply the title and/or format pattern of the attribute to all layers that are associated with the SDS. |
1 | General information configured when creating the SDS. |
2 | SDS parameters configured when it was created. The hyperlink allows you to access the DB that contains the data. |
3 | Spatial information. The extent corresponds to the geographical extent of the elements contained in the SDS. When it has no elements, the values are equal to 0. |
4 | Update schedule. Displays scheduled updates for the SDS. Click the icon to set up an automated update. |
5 | JMap Cloud. This section allows you to share the vector SDS in the JMap Cloud platform. |
6 | Attributes. This section presents a list of SDS attributes. |
7 | References. This section lists the projects and layers that use this SDS. A legend indicates which layers are referenced. |
8 |
The Permissions button appears in the Spatial data section and is enabled when at least one SDS is selected. It is also displayed in the SDS configuration interface.
This section has two tabs: Permissions and Owners. The owners are the only ones who can manage the administrative permissions for the SDS, manage the list of owners and delete it.
A list of users and groups with permissions appears in the Permissions tab. Click on to add new users or groups.
Available users and groups are configured in the JMap Server section of JMap Admin. Refer to the Users and Groups section for more information about managing users in JMap Server.
Only administrator permissions are associated with spatial data sources.
Spatial data sources (SDS) can be shared in order to be accessed by other JMap Server instances. This way, data can be stored in a single location but is accessible from several JMap Server instances.
In JMap Admin, you can share a spatial data source by granting the Remote access permission to one or more users on this spatial data source. This choice must be consistent with the user who established the connection from the JMap Server that must access the shared spatial data sources.
Refer to sections Spatial Data Source Permissions and JMap Server to JMap Server Connections for more information on this topic.
Once a spatial data source has been shared, a icon displays in the list of data sources, in the Shared column.
You can share a SDS with JMap Cloud, a cloud based platform developed by K2 Geospatial.
You must first connect to JMap Cloud. The JMap Server Settings section provides details on this topic. If this step is not completed, a message indicates it in the JMap Cloud section of the SDS configuration interface.
To share or synchronize the SDS with JMap Cloud, in the configuration interface of the SDS, in the JMap Cloud section:
Press Synchronize with JMap Cloud. A window opens and offers you several options:
Copy: A copy of the SDS (data and configuration) is created in JMap Cloud. No link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data will not be synched with JMap Cloud.
Copy and synchronize manually: A copy of the SDS (data and configuration) is created in JMap Cloud. A link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data is not synched automatically with JMap Cloud. You must click on to launch an update.
Copy and synchronize automatically: A copy of the SDS (data and configuration) is created in JMap Cloud. A link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data is synched automatically with JMap Cloud. You can also click on to launch an update.
Select one option and press OK. When the SDS is synchronized with JMap Cloud, the JMap Cloud section presents the following information:
Id: The JMap Cloud spatial data source ID.
Status: The current spatial data source status. While synching, this show the current sync task. Otherwise, it shows the JMap Cloud spatial data source status.
Last update: The last time that the spatial data source was synched.
Automatic synchronization: If ON and an update occurs on JMap Server, the data will be synched automatically with JMap Cloud.
Once a spatial data source has been synched, a icon displays in the list of data sources, in the JMap Cloud column.
Press to remove the JMap Server → JMap Cloud link for the SDS. It will not be possible to manually or automatically sync this spatial data source. The spatial data source in JMap cloud is not deleted.
Press to start synchronizing the SDS with JMap Cloud.
This icon allows you to provide the title in multiple languages.
This article offers more details: .
The section provides details on this function.
Clicking on the will open a window, allowing you to configure its properties.
These buttons allow you to access to the and sections, to make the (the button only appears for vector SDS), to it, it or edit it.
Remote access
Allows a user to access this spatial data source through a JMap Server to JMap Server connection.
This permission must be granted to the user account through which the secure connection between both JMap Servers was established.
For more information on this topic, refer to sections JMap Server to JMap Server Connections and Sharing Spatial Data Sources.
Administrate spatial data source
Allows an administrator to modify the configuration of the spatial data source.
Access spatial data source
Allows an administrator to create layers that take their data from this data source.