The Permissions button appears on the Layers tab in a project's configuration interface and is enabled when at least one layer is selected. It is also displayed in the layer's configuration interface.

This section has two tabs: Permissions and Owners. The owners are the only ones who can manage the administrative permissions for the layer, 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.

Layer permissions are divided into two categories: administrator permissions and user permissions.

Administrator permissions

User permissions

The general settings section of a layer is available in the General tab of the layer configuration interface.

General

Scale thresholds

Scale thresholds are used to control the visibility of a layer according to the scale of the displayed map. This is useful when you want to hide elements of a specific layer beyond (or under) a certain scale. For example, you might not want to display the local street layer when looking at the whole territory of a country. Using the thresholds, you could specify that the local streets are to be visible only when looking at a map with a scale greater than 1:100000. In that case, you would specify a minimum scale of 1:100000, without indicating a maximum scale.

Dynamic refresh

The dynamic refresh of the layer is used to automatically reload the data of a layer after a configured delay, without the need for the user to manipulate the map. This can be useful for layers that contain data that is updated regularly, such as layers of vehicle tracking (AVL). This is an alternative to the use of layers by region to have dynamic data.

The layer configuration interface allows you to access layer information as well as parameter configuration functions such as style, labels, or reports. Tabs also provide access to the same functions.

The raster layer configuration interface contains the General information, Layer parameters, JMap Cloud and Visibility thresholds sections and General and Style tabs.

Attributes

The Attribute configuration window contains three tabs: Metadata, Statistics, and Attribute sample.

The Statistics tab provides simple statistics about the attribute. The Attribute sample tab displays the value of the attribute for a sample of layer elements.

The style of a layer determines the graphical representation of its spatial elements on the map. For example, the style of a line is determined by its thickness, color, dash pattern, etc. In JMap, each layer can have multiple styles. The style used depends on several factors.

Different styles can be configured for different scales. For example, a layer can have a single style for all scales while another layer can have one style for scales greater than 1:20000 and another style for scales smaller than or equal to 1:20000.

Layers also have selection styles. These styles are used to display selected elements at different scales. The selection styles are generated automatically from the layer styles but they can be customized for each layer.

When a thematic is active on a layer, the style of each element is determined by the value of its attributes and the thematic's parameters. See Thematics for more information.

As of JMap Server Jakarta, polygon layers with three-dimensional representation are supported in JMap NG applications. This representation of a third dimension is called an extrusion, and it can be configured when defining the style of the layer. The Extrusion section explains the details of this configuration.

Managing layer styles

You can define one or more styles for a layer.

By default, one style exists for each layer and it covers the full possible scale range.

The Style tab in the layer configuration interface allows you to manage the layer's styles.

To add a new style, press Add. In the style configuration interface, you must define the maximum scale from which the new style will be used. Its minimum scale will automatically be set to infinity or to the maximum scale of the next style.

To remove a style, select it from the list and press Delete.

When deleting styles, the remaining styles will be adjusted to cover the full possible scale range.

Once you have configured one or more styles, you can click on Create template (located to the right of each style) to create a new style template from one of the layer's styles. The style template will automatically be linked to the layer. See Style Templates for more information.

JMap Pro users can change the style of layers and save their changes by creating cartographic contexts. These contexts can be shared with other users and made public to all users who access the application.

JMap Web and JMap NG users can save a map by creating a customized map.

When the JMap administrator modifies the style of a layer, the JMap Pro, JMap Web and JMap NG users working with contexts may not be able to view the style changes made by the JMap administrator. To force the update of the layer style in the contexts, click on Force update... (located to the right of each style). By doing so, the style changes will be reflected in all the contexts of JMap Pro applications and in all the customized JMap Web and JMap NG maps that contain the layer.

Creating or Modifying a style

You have the option to use an existing style template or to configure your own style. If you want to use a style template, click on Use a style template. You will then choose to refer to it or to copy it.

If no style template is used, you need to configure the parameters that will define the style. Start selecting Default style.

Style configuration interfaces are different depending on the type of element (points, lines, polygons, text, etc.). Some style parameters are common to many element types but others are specific to certain types.

Antialiasing is a method of representing perfect, continuous vectors on imperfect, discontinuous display devices so that they look as perfect as possible. In every style configuration section in JMap Admin, antialiasing is enabled by default, which improves the appearance of your maps. However, display performances are reduced when antialiasing is enabled, so use it judiciously.

The following figure shows an example of a polygon border with antialiasing (left) and without antialiasing (right).

Partial object transparency can be used for every type of map element. A map element with a transparency value of 0% will be completely opaque while one with a 100% value will be invisible.

The following figure shows an example of a polygon with a transparency value of 50% (left) and one with a transparency value of 10% (right).

Styles for points

Styles for lines

Styles for polygons

Styles for annotations

Styles for images

Selection style

There is a selection style for each style of the layer. The selection styles are used to represent the elements when they are selected on the map. By default, the selection styles are generated automatically using the layer's basic styles and the project's default selection color.

To modify the selection style, unselect the Generate from default style option and adjust the style parameters as needed.

Extrusion

The style of polygonal layers allows you to configure a three-dimensional representation of the polygons.

In the configuration interface for the layer's style parameters, under the Extrusion section, check Enabled to enable extrusion in JMap NG applications. This function is disabled by default.

Click on Configure to open the extrusion configuration window.

Click on Delete to delete the extrusion configuration.

Analysis

In addition to configuring the style of a layer, you can also create graphical representations to analyze the distribution of point data.

Clustering

Clustering, as its name implies, creates clusters of points on the screen. Special symbols are used to graphically represent these clusters on the map and display the number of elements they contain.

Heat maps

Heat maps are used to graphically represent the concentration distributions of a type of object or event on the territory. The more the color of a zone is intense, the more the concentration is high.

Each layer of a project in JMap takes its data from a spatial data source. Thus, before layers can be created, the related data sources must already exist (see Creating Spatial Data Sources for more information).

To create a new layer, press Create in the Add menu of the Layers tab of a project.

Note that the new layer will have the same name as the data source by default. The name can be changed later.

The next steps are different for vector layers and raster layers. Note that creating a raster layer is also different for each type of raster data source. Jump to the corresponding section below.

Creating a vector layer

The request mode determines how the vector data is managed by JMap Server. It can greatly influence the system’s overall performance.

Two tile loading request mode are available: automatic and manual. You can edit the layer at any time and change the request mode.

Advanced parameters

Most of the time, the following advanced parameters don’t need to be modified.

Creating a raster layer based on a WMS data source

To create a raster layer based on a WMS spatial data source, you need to tell JMap what data to request from the WMS server.

The WMS server publishes a list of all the layers it can serve and their properties. In JMap, the WMS layer creation interface allows you to select the layers to include in the WMS layer you wish to create.

JMap Server offers two modes of connection to the WMS server: Direct and Server.

Direct mode implies that the JMap Server application communicates directly with the WMS service that returns the image. Pro, Web, NG and Survey applications support this option.

Server mode implies that the application asks JMap Server to communicate with the WMS service and return the image. If the application does not support this option, the Direct option is used automatically. Pro and Web applications support this option.

Creating a raster layer based on a GDAL or ECW/ECWP data source

Creating a raster layer from a WMTS data source

Importing layers

You can add a layer to a project by importing it from a project that has been exported from another JMap server. The Exporting and Importing section provides details on exporting and importing a JMap server’s resources.

When you select Add / Import… the Importation wizard will guide you through the process to import one or more layers from the project where they are found.

1. To start the process, select the Importation file. Click on Browse to access the File browser.

2. Select the .properties file that contains the project whose layers you wish to import.

3. Click on Next.

4. Select the Project that contains the layer you wish to import.

5. Select the Layers to import.

6. Click on Next.

7. If the project in which you are importing the layer contains a layer with the same name as the one you are importing, select an option to resolve the conflict between these layers: Create a new layer with a different name, Replace the existing layer or Use existing layer.

8. Click on Next.

9. If the JMap Server in which you are importing the layer contains a spatial data source with the same name as the data source of the layer you are importing, select an option to resolve the conflict between these data sources: Create a new data source with a different name, Replace the existing data source or Use existing data source.

10. Click on Next.

11. A summary lists the number of imported resources for the project: layers, databases, remote connections, spatial data sources, style templates, and metadata templates.

12. Press Import. The layer is added to the project and a new spatial data source is created in JMap Server.

Publishing layers

A layer must be published to be accessible to the users.

When a new layer is created, it is not published by default. This allows you to do further configuration tasks on the layer before making it available for the users. For example, it is important to configure visibility thresholds appropriately according to the scale before the layer can be seen by users.

After layer creation, you must press the Publish button in the layer’s detail section.

You can also publish a selection of layers, from the Layers tab of the project configuration interface. As soon as a layer is selected the Publish button becomes active.

Mouseover bubbles are meant to display information about the elements they are pointing to. This information includes text, attribute values, hyperlinks, images, etc. The JMap administrator determines what information is displayed in the bubbles of each layer.

The content of mouseover bubbles can be formatted using HTML tags. Mouseover bubbles can also contain JavaScript programs.

The Mouseover tab of the layer configuration interface provides the tools to configure it.

Providing mouseover content

You must provide the text that will be used as the content of the bubble. This text can be comprised of static parts (displayed as is), variable parts (replaced at display time by another value), simple JavaScript programs, and HTML tags. For instance, the elementValue(city) function will be replaced at display time by the value of the city attribute for the pointed element.

Mouseover syntax

The mouseover syntax is comprised of various functions that will determine the content of the bubbles. Functions and their parameters are generally not case sensitive. For instance, ev(city) is equal to Ev(CITY).

The following table explains the various available functions:

HTML content

The content of the bubble can be formatted using simple HTML tags. Mouseover bubbles do not support CSS or advanced tags such as <DIV>. The following HTML tags are supported and frequently used in mouseover:

<B>, <I>, <U>, <A>, <IMG>, <TABLE>, <BR>

You can insert hyperlinks in mouseover bubbles. These hyperlinks can be clicked, and they allow users to open HTML pages or to open or download files.

Examples

Locating map elements or coordinates using mouseover

Mouseover supports a function to locate map coordinates or elements using a special URL syntax. A hyperlink is displayed in the bubble, and when it is clicked, the map locates the specified element(s) or region. This function is only available in JMap Pro.

Using a URL to display content

You can specify a URL that opens an HTML page to display in the mouseover bubble (only supported in JMap Pro). The HTML page will occupy 100% of the bubble. The syntax is as follows:

$URL{http://awebsite.com}

The specified URL can be static or it can come from an attribute. It can also use attribute values as parameters, as shown below:

$URL{http://awebsite.com?param1=ev(ATTRIB_A)&param2=ev(ATTRIB_B)}

Thematic mapping is the production of maps to express information about a specific phenomenon. Examples of thematic maps include: polygons representing sectors of a city colored differently based on the crime rate of each sector; points representing cities displayed using different symbol sizes based on the population in the city, etc.

In JMap, you can create thematic maps using the bound attributes of a layer. Depending on the values of their attributes, map elements will then be displayed differently. Using JMap Admin, you can create as many thematic maps as you want and you can also create many thematics using the same layer.

In JMap, there are two main categories of thematics: and .

To create a thematic, press Create in the Thematics tab of the layer settings.

Classification

Thematics that use a classification will separate map elements into a finite number of categories (also called classes), each having a specific style. When a map element belonging to such a thematic is displayed, it uses the style of the category it is part of in order to render itself on the screen.

Creating a graduated styles thematic

Graduated styles thematics use a graduation of one or more visual variables to represent the elements of the different categories. Examples of such graduations include: the fill color of polygons that is graduated from white to red, the size of point symbols that is graduated from size 1 to size 5, the line width of elements that is graduated from 1 to 4, etc. In all cases, there is a finite number of categories and every element of the layer falls into one of those categories. Only a numeric attribute can be used for this type of thematic.

To create a new thematic of this type, you need to select the numeric attribute to use, define the number of categories, select the range calculation method, and define the category styles.

The next section allows you to define the styles of the categories. There are two possibilities: create custom range styles or use predefined color schemes.

Custom range styles

You must define the from and to values of the style by indicating the style variables that will vary (e.g. border thickness, symbol size, fill color, etc.). The category styles are then generated by interpolation between the from and to styles. Optionally, a third style can be used to create an inflexion point. If an inflexion is defined, the generated styles will pass through the inflexion point at the specified position in percentage. The interface is different based on the element type of the layer.

Color schemes

Instead of manually defining styles, you can select a color scheme to generate the styles of the thematic's categories.

Creating a graduated symbols thematic

Graduated symbols thematics draw symbols superposed on the elements they qualify. The symbol sizes are graduated according to a finite number of categories based on a numeric attribute. The symbols can be used with any type of map element. Only numeric attributes can be used for this type of thematic.

Creating an individual values thematic

Individual values thematics represent all elements that have the same attribute value with the same style. This type of thematic is not using a range of values for each category but rather a specific value. The maximum number of unique different values is 512. If your layer has more different values, it will not be possible to create this type of thematic on that layer. Numeric and alphanumeric attributes can be used with this type of thematic.

To create a new thematic of this type, all you have to do is select the attribute to use and follow the steps of the thematic configuration wizard:

Creating an individual custom values thematic

Individual custom values thematics are similar to individual values thematics except that you can define your own values, instead of being limited to values already present in the data. This is useful when you create thematics using a data set that does not contain all the known possible values for an attribute. When new data is later added to this data set, the new values will be handled properly by this type of thematic.

Proportional quantities

Proportional quantities thematics represent map elements using a continuous variation of a visual variable (e.g. symbol size, fill color, etc.) based on a numeric attribute or set of attributes.

Creating a proportional symbols thematic

Proportional symbols thematics draw circular symbols superposed on the center of the elements they qualify. The symbol sizes are determined by interpolation between the minimum and maximum values of the attribute. Only numeric attributes can be used for this type of thematic.

To create a new thematic of this type, you need to select the numeric attribute to use and define the from and to styles. The symbol size and color will be interpolated between the from and to values.

Creating a pie charts thematic

Pie charts thematics draw pie chart diagrams on the center of the elements they qualify. This type of thematic works with one or many numeric attributes. Each part of the diagram (piece of the pie) is associated with a different attribute. The size of the diagram is proportional to the sum of the attribute values. Only numeric attributes can be used for this type of thematic.

To create a new thematic of this type, you need to select one or more numeric attributes to use and define the chart style.

Creating a bar charts thematic

Bar charts thematics draw bar chart diagrams on the center of the elements they qualify. This type of thematic works with one or many numeric attributes. Each bar of the diagram is associated with a different attribute. The size of the diagram is proportional to the sum of the attribute values. Only numeric attributes can be used for this type of thematic.

Methods for calculating ranges

Several different methods can be used to calculate the ranges of values for the categories of thematics using classifications. These methods are described below.

Legend

Once the thematic has been created, you are brought to the interface that displays its general information and that allows you to specify the legend, give titles to the classes, and edit or delete the thematic.

Enabling and disabling thematics

Enabled thematics are displayed automatically when the layer is displayed in JMap on the client. Disabled thematics are still available but are not displayed by default. They need to be enabled by the user to be displayed. You can enable and disable thematics from the thematics section in JMap Admin.

Reordering thematics

In JMap applications, thematics are displayed in the order they are defined in JMap Admin. It is important to set the order appropriately because some thematics can completely hide others if they are placed on top. Use the Modify menu from the list of thematics in order to modify their order.

Deleting thematics

You can delete a theme by selecting it and pressing Delete.

Form configuration of a layer is about designing the form and establishing validation rules.

Form Layout

The interface of the form designer allows you to define the content and layout of the forms used to enter attributes and perform queries.

Forms are organized in a grid, and you can configure the number of rows and columns. Columns and rows can be added to the grid at any moment. All empty rows at the bottom of the form and empty columns at the right of the form will be automatically eliminated when the form is saved.

Each cell of the grid can contain a component of the form (label, text entry field, value list, etc.) but each component can also span several cells horizontally.

Each form can have one or more sections. The user can move from one section to another within a form. This can be especially useful if the form is long or complex.

The following image shows the main parts of the form designer.

Most form components must be associated with either a layer attribute, a database field or a search criterion, depending on the type of form created. The Label, Photo, and Group components are exceptions to this rule.

Component settings

Each type of component has its own configuration window. The settings allow you to control the behavior and appearance of the component. The following table describes some of the settings that are common to several components. A comprehensive description of available components is provided further below.

The following table describes the various components available to create forms and their specific settings. Note that some components are not available to create attribute queries.

Functions

The following functions can be used to initialize form components.

Component validation rules

The rules that you define at the component level allow in particular to:

• Make a field “read-only” or “required” according to the values of other fields of the form.

• Calculate the values of certain fields.

The rules at the component level allow three types of expressions:

Form validation rules

The rules validate the values of the fields on the client side, that is, the values that the users of JMap applications enter in the forms. The validation takes place when the form is saved, which is not done if the rules are not respected.

To configure the rules of a form or a subform, open the configuration interface of the form or subform that interests you:

1. From a form's configuration interface, press the Rules button. The interface displays a table of the rules configured for the form.

2. Press Create to create a new rule or press a rule name to edit it.
3. Press Save.

You can create multiple rules for the same form.

Information reports are used to display descriptive information regarding map elements. These reports can display attributes extracted from the underlying spatial data source or information from databases outside JMap. Each layer can have zero, one or more reports. The information reports are presented as web pages or PDF documents.

The Reports tab of the layer configuration interface provides the tools to configure reports.

The tab shows the list of existing reports for a layer. In JMap applications, reports are presented in this order. You can change the order using the Modify menu.

To create a new information report, press Create.

To delete a report, press Delete.

Creating a report

There are three different types of reports: Basic, Advanced and Custom.

Basic

Basic reports are generated as web pages. They contain features to be printed and exported in Excel. Tables containing the values can be sorted by clicking on the column headers. You can also configure the names of the fields to be displayed in the reports.

Advanced

Reports can be generated in HTML or PDF format. Geographic map integration is also supported.

Report templates

With advanced reports, you can choose the report template you wish to use.

By default, two templates are provided with JMap: a basic report template and a report template with an integrated geographic map. Each one of these templates is also available in two versions: one version is for a single element and the other is for a selection of multiple elements.

The report template files (.rpttemplate) are placed in the JMAP_HOME/applications/templates/reports directory.

Your templates must be placed in the single or multiple sub-directory, depending on whether they are in single element or multiple element version.

Custom

Custom reports are external to JMap and can be called using a URL. These reports can come from reporting tools (e.g. Crystal Reports, Jaspersoft, etc.) or from simple web pages.

A special syntax allows you to format the parameters to be passed in order to open the report.

Supported variables in the URLs of custom reports

Report data sources

Basic and advanced reports can take their data from layer attributes or from an external database connected to JMap.

Current layer

Select the Current layer option to create a simple report that will only query the layer attributes (read below for the External database option). Afterwards, select the attributes to include in the report using the check boxes. Only the selected attributes will be displayed to the user; the others will be excluded from the report. Lastly, you can specify titles for the attributes; these will be displayed to the user instead of the actual attribute names.

External database

Selecting the External database option will instruct JMap to display information taken from another database, instead of the layer. This option allows you to query any database that has a field corresponding to one of the layer's attributes.

Captions

For reports that take their data from an external database, you can define the names of the fields to be displayed in the report, instead of using the field names in the database. Click on Captions to define these field names.

In JMap, labels are text that is related to map elements. They are used to display information about the elements on the map. For example, you can use labels to display the city names for a layer of points representing cities.

Labels can either be placed manually using the labeling tool or generated automatically by JMap at display time. Depending on the type of elements of the layer, the labeling configuration section can slightly vary.

The following figure shows an example of curved labels (left) and labels with a frame (right).

The following figure shows an example of of labels with a background symbol.

Labeling is configured by specifying text that defines the label's content; this text can contain static parts, variable parts (functions) and JavaScript programs. At display time, functions are executed and replaced by the result. For example, the ElementValue(attrib) function (or ev(attrib) in its short form) will be replaced by the value of the corresponding attribute. JavaScript programs can be used to perform operations on attribute values. Label text can span multiple lines.

The functions supported by labels are the same as those supported by mouseover. For more information on these functions, refer to the Mouseover section.

Automatic labeling

Automatic labeling adds labels to map elements automatically, without user interaction. For each vector layer, you can enable or disable automatic labeling and define scales between which automatic labeling will be activated. It is often useful to set a minimum scale limit for automatic labeling to avoid overcrowding the map.

Also, in order to avoid overcrowding the map, three tools allow you to control the order or priority in the position or display of the labels: dynamic position, layer priority, and priority by attribute.

The sections Layer Attributes Forms, Database Forms and Attribute Query Forms describe the steps to create forms and subforms. The examples mentioned refer to the tables in the following figure:

Dynamic filters are used to display certain elements of the layer that match the user's criteria.

Dynamic filters are defined using an attribute, an operator, and values for the attribute. A dynamic filter can be composed of several attributes. Operators vary depending on the attribute type.

• Text-type attributes provide full or partial match operators as well as the presence of null values. Up to 2048 unique values are supported in drop-down menu mode. For attributes who have more unique values than this number, value selection is done by entering the values in the range.

• Numeric type attributes offer quantitative operators.

• Date type attributes provide time operators and calendars for choosing dates. Dynamic time operators can also create mobile windows from a selected date.

To create a dynamic filter:

1. On the Dynamic Filters tab in the layer settings interface, press to add an attribute.

2. Select an operator and values in the appropriate ranges. You can add as many attributes as you want. To remove an attribute from the filter, select it and click on the minus icon .

3. Check the Enabled box to make the dynamic filter active when a user opens an application.

4. Click on Save to save the dynamic filter.

5. Click on the filter name to open its interface and edit it.

Filter operators

equals: This operator filters a layer's elements to display the elements whose attribute value (regardless of its type) is equal to one of the values selected by the JMap administrator.

does not equal: This operator filters a layer's elements to display the elements whose attribute value (regardless of its type) is different from the values selected by the the JMap administrator.

greater than: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is greater than the value selected by the JMap administrator.

greater or equal to: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is greater than or equal to the value selected by the JMap administrator.

less than: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is less than the value selected by the JMap administrator.

less or equal to: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is less than or equal to the value selected by the JMap administrator.

contains: This operator filters a layer's elements to display the elements whose attribute value (text) contains the value selected by the JMap administrator.

does not contain: This operator filters a layer's elements to display the elements whose attribute value (text) does not contain the value selected by the JMap administrator. This is the same as making a query with the WHERE clause attribute_name NOT LIKE '%value%'.

is empty: This operator filters a layer's elements to display the elements whose attribute (text) does not have a value.

is not empty: This operator filters a layer's elements to display the elements whose attribute (text) has a value.

is null: This operator filters a layer's elements to display the elements whose attribute value (regardless of its type) is null.

is not null: This operator filters a layer's elements to display the elements whose attribute value (regardless of its type) is not null.

is between: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is within the range defined by the two values entered by the JMap administrator.

is not between: This operator filters a layer's elements to display the elements whose attribute value (numeric or date) is not within the range defined by the two values entered by the JMap administrator.

last: This operator filters a layer's elements to display the elements whose date attribute value is within the range (expressed in years, months, week(s), day(s), hour(s)) defined by the JMap administrator.

interval: This operator filters a layer's data based on time ranges defined using a start date, an end date and a reference date. The user therefore has a tool to display data that varies over time.

The layer must contain at least two date and/or timestamp attributes, one of these being the start Date/Time, and the other being the end Date/Time. The values of these dates can be NULL to indicate a start date that goes a long way back or an end date that is very far in the future.

A reference date is also needed. This date can be a specific date (in the past or in the future) or a current Date/Time, which indicates the present moment.

Only layer elements whose reference date is between the start and end date are displayed in the map.

The following figure illustrates this filter.

In JMap, forms are used for attribute queries to enter the search parameters, to enter attribute values of editable layers and to manage data stored in databases. This is always done in relation with the elements of a layer. A type of form called a subform can also be accessed from another form.

The JMap administrator designs the forms using the form designer. Afterwards, users can use them in JMap Pro, JMap NG and JMap Survey. Depending on access permissions, users can use data entry forms to view, add, modify or delete data.

The following sections explain the form creation process in detail and the functionality of each type of form.

Database forms are used to manage data stored in databases that are external to JMap. They allow you to add new data as well as modify or delete existing data.

Each database form has its own permissions to control which users can make changes to the data.

These forms can be used to manage data using a 1 to 1 relationship with a layer’s data. In this case, a record is added when an element is created, and this record is usually deleted when the element is deleted.

They can also be used to manage data using a 1 to N relationship with the layer data. In this case, a special type of form called a subform is used and is always associated with a table form component. Refer to the section for more information on this topic.

Configuring this type of form is an advanced JMap function that requires writing SQL queries to extract, add, modify and delete data.

Creating a database form

To create a database form, in the Form section of the Forms tab of the layer configuration interface, press Create.

You must enter a name for the new form. Afterwards, you must select the type of form to create, Database, then select the database containing the data to be used in the forms.

At the following step, a window allows you to enter the form’s SQL queries. These queries are used to extract, add, modify, and delete data.

Only operations for which SQL queries have been provided can be performed.

SQL Query Syntax

A special syntax is used for SQL query configuration. In general, each line of this syntax must end with a semicolon (;). The syntax is not case sensitive.

The following table provides a detailed explanation of how this syntax works.

Form properties

The following table provides a detailed explanation of each parameter in the database form creation window.

Subforms

Subforms are database forms that are opened from a Table component that exists in another form. They are normally used to manage data that has a 1 to N relationship with the layer’s elements. They could be used to manage data for inspections on assets (N inspections can be associated to the same object), for example. They are configured similarly to the other database forms.

Creating a subform

To create a subform, open the Subform tab on the Forms tab in the layer parameters menu, then click on Create.

You must enter a name for the new form and select the database containing the data to be used in the forms.

At the following step, you must configure the SQL queries of the subform, as explained above for the creation of a database form.

Nested subforms

Several levels of subforms can be nested in a subform. They are used to manage data having a 1 to N relationship with the subform’s records. For example, they can be used to manage the data of interventions arising from an inspection performed on an asset (N interventions can be associated with 1 inspection).

A nested subform is opened from a Table component found in the subform it is associated with.

The following figure shows a preview of the nested subforms from our example, in JMap Pro.

Permissions of database forms

Database forms have their own permissions. The Permissions button appears in the form configuration interface.

The Permissions section has two tabs: Permissions and Owners. The owners are the only ones who can manage the administrative permissions for the project, manage the list of owners and delete it.

Available permissions are described in the table below.

These forms are used to enter the attribute values of an editable layer.

The user must have the required permissions to modify the values of a layer’s attributes. Refer to the section for more information.

Creating a layer attributes form

To create a form for entering attributes for a layer, in the Form section of the Forms tab of the layer configuration interface, press Create.

Enter a name for the new form. You must then select the type of form to create, Layer attributes. Click on Save.

Afterwards, select Form layout in the settings menu to go to the form designer and add components.

The component provides the attribute value, and the value is updated when the user closes the form and saves the changes. Refer to the section for more information.

Permissions for Layer Attribute Forms

The Permissions button appears in the form configuration interface.

The Permissions section has two tabs: Permissions and Owners. The owners are the only ones who can manage the administrative permissions for the project, manage the list of owners and delete it.

The available permission is:

JMap Server allows you to share layers between projects that are on the same server or that originate from remote servers that are connected. Layer sharing allows you to manage data more effectively (avoids duplication, saves time) by reusing existing layers instead of creating new layers in each project.

Referenced layers cannot be modified directly, except a few basic settings. Only the original shared layer can be modified.

From the Kathmandu version, JMap Server can share or synchronize layers with the cloud-based geospatial platform JMap Cloud developed by K2 Geospatial. So JMap Server layers with their configuration can be consumed by JMap Cloud users.

The figure presents the layer sharing between projects on the same server and on different servers. The properties of the Rivers layer cannot be modified in projects 1 and 3. The original layer is in project 2.

Sharing layers between projects on the same JMap Server

Sharing layers between different JMap Servers

If you wish to share a project’s layers in order to access them from another JMap Server, you must assign a special remote access permission to a user for these layers. In order to do this, access the project Layers tab for which you wish to share these layers.

1. Select one or more layers.

2. Click on Permissions.

4. Select the Remote access permission.

To stop layers from being shared, simply remove the Remote access permission from these layers.

Accessing shared layers

To access existing layers from different projects located on the same JMap Server or shared layers on other JMap Servers:

1. Click on Add and select Clone / Reference in the Layers tab of the project to which you would like to add these layers.

3. Select the project from which you wish to clone or reference layers. Once the project has been selected, the list of available layers displays.

4. Select the layers you wish to clone or reference and move them to the list on the right.

5. Select the Clone or Reference option.

If you choose the Clone option, the selected layers will be duplicated towards your project. They will be exact copies of the original layers, but there will be no connection between the copies and the original layers.

You can modify the copies without affecting the originals.

If you delete a cloned layer, this doesn’t affect the original layer. If you delete the original layer, this doesn’t affect its cloned layers.

However, duplicated layers always use the same spatial data source as the original layer. If this data source is modified or deleted, this will affect the duplicated layers.

If you select the Reference option, the original layers will be accessed by reference. This means that a direct connection will be maintained between the layers of your project and the original layers.

You will not be able to modify these layers in your project. If the original layers are modified, the changes will appear wherever references to these layers exist, after a short delay.

If you delete a referenced layer, the original layer will not be affected. If you delete the original layer, the referenced layers will no longer work and will have to be deleted manually.

Sharing layers with JMap Cloud

You can share a vector layer with the JMap Cloud the geospatial platform developed by K2 Geospatial, by copying or synchronizing it with JMap Cloud.

Sharing a layer from its configuration interface

In the JMap Cloud section:

Sharing layers from the project's Layers tab

Select the layers you want to sync with JMap Cloud and:

1. Press Sync with JMap Cloud.... If all the layers are already synchronized with JMap Cloud, they are directly updated in JMap Cloud. If at least one of the layers is not shared or synchronized with JMap Cloud, a window opens offering you several options regarding the actions to perform (copy or synchronize the layer) and the destination project (create a new project or use an existing project): Copy layer(s): This function creates a copy of the layers (configuration and data) and its spatial data sources in JMap Cloud. No JMap Server → JMap Cloud link is created. If the layers are updated on JMap Server, the data is not synchronized with JMap Cloud. Synchronize layer(s): This function creates a copy of the layers (configuration and data) and its spatial data sources in JMap Cloud. A JMap Server → JMap Cloud link is created. If there is an update of the layers on JMap Server, the data is automatically synchronized with JMap Cloud. Create a new project: Indicate the name of the project that will be created in JMap Cloud to receive the layer. Use an existing project: Select the project on JMap Cloud in which the layer will be copied or synchronized.

A project is composed of an ordered list of layers. Layers are used to display data extracted from spatial data sources.

Vector layers are related to vector data sources and display vector data while raster layers are related to raster data sources. The layer configuration determines the appearance of the data (style of the layer), the visibility thresholds, what information is associated with the spatial data (attributes), etc. Each layer has its own configuration parameters for labelling, reports, thematics, etc.

Specific permissions can be configured for each layer. Thus, some layers can be accessed only by a subset of users authorized to open the project.

The layers of a project can be organized into a logical tree-like structure or hierarchy. This feature is useful to better organize information when working with projects that have a high number of layers. In client applications, users are able to control the visibility of the layers belonging to the same group in one click. Refer to the section for more information on this subject.

Layers can be copied from one project to another or even shared between various projects located on the same JMap Server or on separate JMap Servers. From the Kathmandu version, it is also possible to share layers from JMap with the cloud-based platform JMap Cloud, developed by K2 Geospatial. Refer to the section titled for more information on this topic.

Some JMap Server extensions require the configuration of specific parameters at the layer level.

The layer configuration interface has tabs for each of the extensions that need to be configured at that level.

Once the settings are configured, press Save.