Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
The JMap administrator designs the forms using the form designer. Afterwards, users can use them in JMap Pro, Web, NG and Survey.
Like data editing forms, attribute query forms are created using the form designer. They allow the users to enter query parameters.
Each form component is therefore associated with a parameter of the query ($param1, $param2, etc.).
Unlike the other types of forms, they cannot be divided into sections. In addition, the Photo components are not available for this type of form.
These forms are created when configuring attribute queries, by clicking on Form layout.
When creating an attribute query form, it is important to consider which parameters are required and which are optional in the query definition. For instance, if Required is not selected for a form component, the query must consider this parameter as optional.
Refer to the Creating attribute queries section for more information on optional parameters in queries.
The configuration interface of a project allows you to access information on the project. This interface also contains functions to configure various parameters, such as the initial view of the project in the applications.
The project preview provides a preview of the map, in which you can test the configurations made as they work in JMap Server applications.
JMap Server Lima does not provide a JMap Pro preview of your project. The function of this preview is replaced by the Administration extension displayed when creating a JMap Pro application. The JMap Pro Applications section provides details of this extension.
It opens a JMap Web application in a new browser window.
The preview offers most of the functionality of JMap Web applications and allows you to validate the project’s configuration.
The JMap Web preview does not allow data editing. Data editing can be done in a JMap Web type application.
It opens a JMap NG application in a new browser window.
The preview offers most of the features of JMap NG applications and allows you to validate the project configuration.
The JMap NG preview does not allow data editing. Data editing can be done in a JMap NG type application.
The Permissions button appears in the Projects section and is enabled when at least one project is selected. It is also displayed in the project configuration interface.
This 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.
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 section for more information about managing users in JMap Server.
Project permissions are divided into two categories: administrator permissions and user permissions.
Administrator project permissions define the project administration rights for the users authorized to use JMap Admin. For more information on concepts related to permissions and administration roles in JMap Admin, refer to the section.
User project permissions determine which users and groups can open a project. Access will be denied to users who do not have the appropriate permissions. Security can also be configured at the layer level. For more information on this topic, refer to the section.
Adding the Anonymous user to the list of users authorized to open the project gives users the possibility to open a project without any authentication. This is equivalent to removing all security for opening the project. This is useful for public applications, when no project access control is needed.
Adding the Everyone user to the list of users authorized to open the project allows all users to open the project, including the Anonymous user. This means that the project is accessible to all users, with or without authentication.
Adding the Authenticated users to the list of users authorized to open the project allows any authenticated user to open a project. This is useful for private applications where all users are allowed to open a project but must authenticate themselves.
JMap Web preview also allows you to configure the initial view of the project when it is opened in JMap Web applications. To do this, click on and then on Initial extent. A rectangle displays to delimit the initial extent.
Click on Maximum extent to display the maximum extent. When you close the preview, the geographic coordinates of the initial extent are automatically saved.
1
The project sections are organized into tabs: Layers and Layer Groups, Queries, Image Producer and the configuration interfaces of JMap extensions compatible with JMap NG or JMap Survey.
2
General information configured when creating the project.
3
Project settings. The project’s parameters. They are configured when the project is created. The project’s extent corresponds to the extent of the layers that make up the project. When the project does not have any layers, the values are equal to 0.
4
5
Extensions. This section presents the list of JMap extensions configured for the project. The switch next to the name of each extension enables or disables the extension in the JMap NG and JMap Survey applications which publish the project. The JMap extensions compatible with JMap NG or JMap Survey section provides more details on this topic.
6
References. This section indicates the deployed applications that use this project.
7
8
This section allows you to synchronize/share the project with JMap Cloud.
9
10
Layers. This section shows a list of the project layers and their statuses. Shortcuts allow you to access the interfaces to add and organize layers.
11
These buttons allow you to delete the project, access permissions or edit it.
Administrate project | Allows an administrator to modify the project and its content. |
Access project | Allows an administrator to access a project to view its content and to use it when deploying JMap applications. |
Open this project | Allows a user to open a project from a JMap application. |
Initial view settings. These parameters are specified when the project is created. The initial view is defined by clicking on in the Preview section. By default, the initial view corresponds to the extent of the project. When the project does not have any layers, the values are equal to 0.
Mapbox cache. This section presents the size of the cache for the project’s vector tiles. It also indicates if you want to automatically delete the cache of the vector tiles. You can clear the cache by clicking on .
Preview. This section displays when the project contains at least one layer. It shows a map preview, and you can zoom in or out on it. Click on to open a JMap Web Preview or a JMap NG Preview in a separate window in which you can define the initial view and test the project configurations. You can select a base map for the JMap Web preview: None, OpenStreetMaps, Mapbox maps, and Bing maps, if they are available for your organization.
Attribute queries are used to find and select elements of a map layer using their attribute values or a database associated with the layer.
In JMap Admin, JMap administrators create the queries and their associated forms. Then, users of JMap applications use those forms to enter attribute values to search for. All elements whose attribute values match the values entered are then selected or listed in an elements explorer.
The Queries tab of a project's configuration interface allows you to configure the project's queries.
The Queries tab appears when the project contains at least one layer.
This tab presents a table that displays the query groups. The table shows the number of queries each group contains. The Organizing attribute queries section provides details about the groups.
To create a new query you must position yourself in a group of the Queries tab. The Create a query button is displayed and you can therefore open the query configuration interface.
Parameters will vary depending on the type of query selected.
This type of query is used when the search must be conducted within the data of an external database. The external database must contain a field that links to a layer attribute. A select SQL query is executed in the external database and the values returned are then associated with the layer elements using the link field.
Although search forms are designed to mark fields as required or optional, the where clause of the query must be adjusted to support this option. To accomplish this, any part of the query that is associated with optional parameters must be included between braces ( { } ).
Example of WHERE clause:
CITY = '$param1' and { COUNTRY = '$param2' }
This example searches for cities for which the attribute value CITY is equal to the value of parameter 1 ($param1) entered by the user and who optionally have their value for the COUNTRY attribute equal to the value of parameter 2 ($param2) entered by the user. If parameter 2 is left blank , the entire block { COUNTRY = '$param2' } is removed from the query, along with the and operator, which is now an orphan. Note that the administrator must absolutely define $param2 as optional when designing the form. Refer to the Forms section for more information on designing forms.
Multiple values can be entered with a List (multiple choices) type field in the forms. The values are separated by the delimiter character ; (semicolon). This option can be activated in the WHERE clause of the query. The syntax is as follows:
$multiple{true|false} {$delimiter{;}}
Example:
CITY = '$param1{$multiple{true} $delimiter{;}}'
Searches for cities whose CITY attribute value is equal to one of the values entered in parameter 1. The values are separated by semicolons.
Attribute queries can be modified by administrators. In JMap Dakar and later versions, when a project’s queries are modified, the applications that disseminate the project do not need to be redeployed because the changes are reflected directly.
Attribute queries can be organized into groups. This is particularly useful for projects that have a large number of queries.
To create a new group, click on the Create group buttonon the Queries tab.
To delete a group, select it in the list and click on Delete.
Deleting an attribute query permanently deletes the query and its associated form. To delete a query, select it in the list and click on Delete.
Once a query has been created, it is automatically published. However, you can disable this publication, which will make your query unavailable in applications, but its configuration will still be saved. If you do not want your query to be published, clear the Published checkbox of your query in the query management interface.
When a project contains referenced layers, the queries configured on these layers are automatically available in the project. The project “inherits” these queries.
You cannot modify these queries from the project; they can only be modified in the project that contains the original layer.
If you wish to make changes to a query on a referenced layer, create a copy of the query by clicking on Clone. The configuration interface shows the search parameters that you can modify.
Once the new query has been configured, you can clear the Published check box of the query that was “inherited” from the referenced layer if you no longer want it to be available in JMap applications. If the Published check box is cleared for an attribute query on a layer, that query will no longer be available in the projects that use the referenced layer.
You can also create a new query on a referenced layer as described in the section Creating a new attribute query.
The image producer of a JMap project is used to produce images on demand for that project. These images are used for JMap Web applications. When a user works in JMap Pro, the image producer is not used because the data is transferred in vector format (except for photos).
Normally, the image producer’s settings do not need to be modified because the default configuration is adequate. The following table describes the settings of the image producer.
The layers of a project are displayed in the Layers tab of the project configuration interface. This icon located in the Layers section of the project interface also takes you to the Layers tab.
The table shows basic information about each layer of the project. When you click on the name of a layer, a details section displays.
In this tab you can define the order of layers in the project. The section offers details on this topic.
Buttons allow you to perform management tasks for the layers you select in the table, as well as add new layers to the project.
The icon in the Layers section of the project configuration interface gives you the three options to add a layer to the project.
When you select one or more layers you can grant permissions for the whole set. Refer to .
You can edit different settings for a set of layers. You must select the layers to modify in the List tab of the Layers section of the project. Afterwards, press the Update button, and click on the Bulk edit… option. The Bulk edit interface will open.
Deletes the selected layers.
To modify the order of groups, click on Modify and select Reorder groups. The window that is displayed allows you to drag and drop the groups in order to change their order. To rename a group, click on .
This button allows you to synchronize the selected layers with JMap Cloud. The section provides details on the subject.
Title
Enter a title for the query. Users will see this title in a list of queries.
Layer
Select the layer on which the query will be executed. A search field is provided to simplify layer selection.
Maximum scale
Specify the maximum scale used to present the results on the map. This is used to avoid zooming in too closely on the results.
Max. returned values
Specify the maximum number of elements this query can return. The query will refuse to execute if the return size is higher than this limit. This is used to avoid very long queries that could slow down the system.
Query templates
Basic: With this type of query, the search is only performed on the layer attributes. This is the simplest type of query. External database: With this type of query, the search is performed in an external database that has a field linking to an attribute of the layer. Setting up this type of query is more complex but offers more searching flexibility.
WHERE
WHERE clause of the SQL query used to run the search. Here is where all the search criteria will be defined. Typically, this clause contains numbered parameters ($param1, $param2, etc.) that will be replaced by the values the user enters in the form.
Examples
COUNTRY='$param1'
Selects the layer elements for which the attribute value COUNTRY is equal to the value entered by the user.
The attribute value must perfectly match the value entered ($param1).
lower(COUNTRY) like lower('$param1%')
Selects the layer elements for which the attribute value COUNTRY is similar to the value entered by the user. The attribute value must begin with the value entered ($param1). Since the lower operator is used, the search is not case sensitive.
POP2000>=$param1 and POP2000<$param2
Selects layer elements that have the POP2000 attribute value within the range defined by the two values that were entered ($param1 and $param2).
Form layout
Press this button to configure the query form. See Forms for more information.
Database
Select the database in which you would like to perform your query.
SQL query
Enter the SQL query that will be executed in the database to search for elements.
Example
select * from cities where CITY_LANGUAGE='$param1'
Searches the database selected above, in the cities table. Retrieves all fields of records for which the value of the CITY_LANGUAGE field is equal to the value entered by the user ($param1).
Layer attribute
Among the layer attributes, indicate which one is used to link with the database.
Field
Among the fields returned by the SQL query, indicate which one is used to link with the layer.
Form layout
Click on this button to configure the query form. Refer to the Forms section for more information on this topic.
Memory settings
Maximum size
The maximum amount of memory allotted to the project’s image producer. This memory is used to store the project’s vector data in order to accelerate the production of images. For very large projects, this setting can be increased.
Memory usage
The amount of memory currently used. The left value varies depending on usage. The right value is the maximum amount of memory allocated to the image producer.
Usage peak
Maximum memory size reached since last JMap Server startup.
Memory release
Determines the percentage of memory to be released when the memory of the image producer is saturated.
Thread pool settings
Initial size
The number of threads determines the number of images that can be produced simultaneously.
Maximum size
If the number of threads increases due to high demand, this value limits the number of threads.
Pool usage
Number of threads currently used (left value) out of the maximum number allocated (right value).
Usage peak
Maximum number of threads reached since last JMap Server startup.
View wait timeout
The maximum period before an image request expires. This option is usually disabled.
Change ‘Antialiasing’ | Check if you want to change this setting. |
Change Minimum scale | Check to change the minimum scale for displaying layers. Check Infinity or 1: and in this case, indicate the scale. |
Change Maximum scale | Check to change the maximum scale for displaying layers. Check Zero or 1: and in this case, indicate the scale. |
Change Request mode | Check to change the data request mode. Check the option of your choice. |
Change Description | You can write a new description for the layers. |
Create |
Clone/Reference |
Import… |
Update data sources | Updates the spatial data sources associated with the selected layers. Refer to Spatial Data Sources. |
Update caches |
Update - Bulk edit… |
There are two aspects to organizing layers in a project:
Order of appearance of the layers on the map. Layers at lower positions are drawn first and layers at higher positions are drawn at the end. Top layers can hide elements of bottom layers.
Logical hierarchy based on the nature of the layers. In other words, groups and subgroups of layers that have a logical relationship. For example, there could be a group of layers related to roads, another to hydrography, and another to census. Organizing them in groups makes it easier for the users to work with layers.
You can set the layer order in the Layers tab and the layer hierarchy in the Layer groups tab of the project configuration interface.
In both tabs you can grant permissions to selected layers. The Layer Permissions section provides details about the permissions.
To order layers of a project, open the tab titled List. This section presents the layers in their order of appearance on the map. The lowest position is the first layer to be drawn on the map.
To change the order, you must use the Modify menu located at the top of the column displaying the position of each layer. You can also select one or more layers and move them using the available options (Move up, Move down, Move at…, etc.). The option Reorder layers opens a window displaying all the layers that you can reorder using drag-and-drop actions.
To organize layers in groups, open the tab Layer groups. This section presents the current hierarchy of layers.
By default, all layers of the project are in one unique group called Layers.
To create a new group, press Create group. Fill the layer group parameters as described below:
Once groups have been created, you can move layers towards these groups using the Modify menu located at the top of the column displaying the position of each layer.
Extensions which are compatible with JMap NG and JMap Survey applications must be configured and activated on the project to make them accessible to the users of these applications.
To configure the extension, in the project configuration interface select the tab with the extension name. Once the configuration is complete, press Save.
To activate the extension, slide the extension switch in the Extensions section of the project configuration interface.
The section provides details on configuring extensions in JMap Server.
Check New Value to enable the antialiasing feature. Uncheck New Value to disable the antialiasing feature. The section provides details on this parameter.
The section provides details on this topic.
The section provides details on this topic.
The section provides details on this topic.
Initiates the creation of a new layer. Refer to .
Allows you to duplicate or reference a layer from another project located on the same server or on a different JMap Server. Refer to .
Allows you to import layers one by one from a project exported from another JMap server. Refer to .
Launches the preparation of the vector data cache for the selected layers. Refer to .
Allows you to edit certain layer parameters in batches. The section provides details about this topic.
Name
Enter a name for the new group. The name must be unique.
Description
Optionally enter a description for the new group. This description will be visible to users.
Visible
Makes the group initially visible when the project is opened. All visible layers inside the group will be displayed.
Always listed
Ensures the group is always listed (displayed in the layer management window ) even if it contains no layer. By default, empty groups are not listed. A group can be empty if it contains no layer, if all the layers it contains are not listed or if the user doesn’t have the permission to see the layers of the group.
Image
This option allows you to select an image (an icon) to display with the group of layers.
Press Choose to open the file browser and select the image file.
The image size should not exceed 100*100 pixels.
This option is only available for JMap NG applications. Other application types do not display the image.
