Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The organization's administration functions as well as the management of service subscriptions are reserved exclusively for administrators.
This user guide details the main steps that in JMap Cloud Portal lead to the distribution of JMap Cloud data via a public or restricted access cartographic application.
Each member of an organization has one of three roles in JMap Cloud Portal: administrator, editor, or viewer. The Roles section details the functions specific to each role. Only administrators and editors access JMap Cloud Portal. Viewers access applications that stream data from JMap Cloud. Administrators and editors view all sections of JMap Cloud Portal but only the functions that correspond to their role are activated.
The following figure summarizes the workflow with the roles involved.
This step requires the editor to connect the data to JMap Cloud by creating spatial data sources. These can be GIS files, spatial data servers, satellite images, etc. Files are uploaded and their data is copied into JMap Cloud databases or connections to data web services are created to make the data available to configure projects.
See Connecting Data: Spatial Data Sources for more details on this.
JMap Cloud data is organized into projects. A project contains information about map layer definitions, as well as settings governing access control (security), queries, units, etc. By creating a project, the editor defines the visual appearance of the map and the information it will contain.
See Organizing Data into Projects for more details on this.
In this step the editor creates the cartographic layers of the project. Each layer of the map is associated with a spatial data source. For each layer, the editor defines the style (the way the elements of the layers will be drawn), the labels, the themes, etc. It can also define access control layer by layer.
See Configuring Cartographic Layers for more details on this.
The project is disseminated to end users via mapping applications. Depending on the access controls configured by the editor, the applications may be public or may be accessible through the authentication of the user who holds the viewer role.
The JMap NG User Guide provides details on JMap Cloud mapping applications.
JMap Cloud is a geospatial platform dedicated to application developers who want to easily add cartographic features to their software.
JMap Cloud offers very efficient cloud services and powerful APIs to integrate geospatial data from different formats and systems in order to produce rich interactive maps that facilitate decision-making. The platform implements the latest trends and standards in the geospatial field.
The following figure illustrates the JMap Cloud ecosystem, with its microservices and relations with the systems in place in an organization as well as the applications that allow you to interface with users.
JMap Cloud Portal is the web tool that allows you to manage data, projects, users and technological ecosystem around JMap Cloud through visual interfaces for a given organization. JMap Cloud Portal users can integrate data, create projects and disseminate it to end users through cartographic applications.
The JMap Cloud Portal user interface looks like this:
In the sections, information is presented in table mode and sometimes also in card mode.
In the tables, the rows correspond to the section's resources: organization members, API keys, files, tasks, spatial data sources, etc.
You can select the quantity of rows to display per page: 25, 50, 100. A table can have multiple pages. The footer displays the number of rows on the page and the total number of rows in the table.
For each resource, a menu is displayed when the cursor is placed on the attribute name. The functions offered in the menu vary depending on the resource:
Show information
Edit information
Create a source
Interrupt
Delete
...
The table columns correspond to the attributes. The table header presents the attribute names.
Sort table rows ascending or descending
Hide attribute
Show column
...
A JMap Cloud administrator in your organization will send you an invitation to join the JMap Cloud Portal.
The invitation sent by JMap Cloud contains a hyperlink that takes you to the JMap Cloud Portal login page. The interface for accepting the invitation to join JMap Cloud Portal displays your email address and the field for creating your password.
Once the password is created, click on Continue to progress through the login procedure detailed in the next section. If you already have an account, you can log in directly by clicking on Sign in.
Once you have created your account, you access JMap Cloud Portal via:
The JMap Cloud website when you press the Login button.
The JMap Cloud Portal website:
To continue the connection:
Click on Login to display the JMap Cloud Portal login page.
Enter the email address and password with which to log in to JMap Cloud Portal and press Continue. Once authentication is successful, the following interface prompts you to select your organization.
Click on the organization you want to connect to. A new authentication is performed and you access the JMap Cloud Portal of the selected organization.
The home interface displays the which provides an overview of the JMap Cloud Portal resources for which you have access permissions.
Organization management is carried out in the Organization section of JMap Cloud Portal. This section is structured into four tabs: , , and .
Management of the organization is exclusive to members who hold the Administrator role.
For each attribute, a menu is displayed when the cursor is placed on the attribute. The menu varies depending on the resource, but it offers functions for:
Filter table rows based on an attribute value. When a filter is applied, the icon displays next to the attribute name.
A display of resources in cardboard mode is available in the Projects section. Buttons allow you to add resources in each section except the section.
1
Header bar. Indicates the section of JMap Cloud Portal that is displayed in the main interface. Icons allow you to change language and graphical interface settings. Information of the logged in user as well as functions to change password and log out.
2
Tools bar. Each icon provides access to a section:
3
Access to JMap Cloud Portal documentation. The JMap Cloud Portal version is indicated at the bottom of the bar.
4
Section interface.
: provides an overview of the organization's resources to which you have access.
: contains the functions that allow you to manage the administrative aspects of the organization: members, invitations, etc.
: Introduces functions to create and manage the spatial data sources you have access to.
: contains functions for creating and managing projects.
: contains tasks performed by JMap Cloud Portal.
Icons are enabled or disabled based on the role of the logged in user. See the section for more details.
Roles are categories of JMap Cloud Portal users, defined by a set of general privileges to access and modify the organization's resources.
Each member of an organization has one of three roles:
Administrator
Editor
Visualizer
A user can only have one role.
Each role allows you to perform specific functions and access relevant sections of JMap Cloud Portal. Only users who hold the Administrator or Editor role access JMap Cloud Portal.
The figure schematizes the relationship between the three roles: the administrator accesses all the functions of JMap Cloud Portal and applications, the editor accesses the functions and resources linked to the data while the viewer only accesses the data and functions available in the applications.
An organization administrator is a JMap Cloud Portal user who performs administrative management tasks for their organization, including membership, payments, and API keys.
The administrator:
Create, modify and delete API keys
Configure organization settings
Invites members to join JMap Cloud Portal
Creates, edits information, and deletes organization members
Assigns and modifies the role of each member of the organization
Manages organization extensions
Tasks are performed from the Organization section of JMap Cloud Portal. The Managing the organization chapter offers details on each function.
The admin can also access the Dashboard from where can quickly create API keys.
Additionally, the administrator can perform all the tasks of the Editor role.
This is the default role of a member of an organization.
The editor accesses JMap Cloud Portal functions not related to the organization's administrative tasks. Its main task is to configure the maps that will be distributed through the applications.
The editor:
Creates, accesses, configures, modifies and deletes resources from JMap Cloud
Spatial data sources
Projects
Map layers
These tasks are performed from the Dashboard, Spatial Data Sources, and Projects sections of JMap Cloud Portal.
This is a user who accesses project data and functions through JMap Cloud applications.
This user does not access JMap Cloud Portal.
The viewer:
Access a project with its data layers
Navigates the map and interacts with the data in different ways (interactively selecting items, performing searches, displaying information, etc.)
Can edit the geometries and/or attributes of a map layer if they have edit permissions for the layer
The first step in the workflow that leads to map distribution is connecting JMap Cloud to spatial data through the creation of Spatial Data Sources (SDS).
In the context of JMap Cloud, a spatial data source is any source that provides spatially referenced data.
JMap Cloud allows you to create SDS from vector or raster data files, WMS/WMTS services, vector tile services and feature services.
Vector and raster SDS can also be created from JMap Server when a JMap Server administrator synchronizes data sources, layers, or entire projects from a JMap Server to JMap Cloud. The details of this synchronization are presented in the JMap Server Administrator Manual.
The Spatial data sources section of JMap Cloud Portal provides functionality for uploading files to create data sources as well as directly creating spatial data sources from new files and data services.
These spatial data sources are subsequently available to create project map layers.
This section displays a table of your organization's API keys. For each API key the table displays the title, the unique identifier (Id), the name of the user who created it, the creation date and the expiration date.
The menu displayed in the header of each attribute in the table allows you to sort the keys, filter them, hide or display attributes.
To add an API key:
Click on Create new API key.
Enter the name for the key, the expiration date, and select the role to assign to the API key from the drop-down list (only Editor and Viewer roles can be assigned to an API key). Fields marked with an asterisk are mandatory.
Click on Create. A message displays: This is a private API key that should be kept secret and secure. Once this window is closed, it will no longer be possible to see the API key again.
If you want to copy the API key to the clipboard for use in another context, click on .
Press OK. The key is created and displayed in the table.
Place the pointer over an API key to display the key's menu .
Click to access the available functions: Display information and Delete.
Click on Display information to open the key's interface. This displays the title, the name of the user who created it, their role, email and expiration date.
If you want to copy the email to the clipboard, click on .
Click on Delete if you want to delete the key. Deleting an API key has resource impacts. The Delete an API Key section provides details on this topic.
To better manage your organization's API keys, you can delete keys that are no longer useful.
Deleting an API key has resource impacts because an API key can own resources (data sources and projects with its layers).
To retain resources, you can transfer their ownership to other members of the organization. If you don't do this, the resources are deleted along with the API key.
To delete an API key:
Click on Delete. A message asks you to confirm your intention.
Press OK. If the selected API key owns resources, a list of members with the Editor role is displayed for you to select the member to transfer ownership of the API key resources to. If the API key does not own resources, a message asks you to confirm the deletion.
If so, select the Editor member who transfers ownership of the assets to. The selected member is registered as an owner in each data source and project that owns the API key.
Click OK to confirm deleting the API key. API key resource access permissions (access control list, ACL, entries) are removed. Resources that are solely owned by the API key are permanently deleted.
Deleting an API key is irreversible. The API key is physically deleted from JMap Cloud.
Place the pointer over the API key you want to delete to display the menu .
JMap Cloud creates spatial data sources (SDS) from multiple vector and raster data file formats: CSV, KML, DXF, DWG, SHP, TAB, GeoPackage, FileGeoDatabase, GeoJSON, GeoTIFF.
Files can be uploaded when creating a spatial data source or uploaded in advance. For more information, see the Upload Files section.
An SDS can include multiple vector or raster data files that form a continuous map. For example, a common CAD practice is to separate the territory into rectangular tiles. By reading all tile files together, JMap Cloud can recreate continuous maps as long as the files contain the same data structure (geometry, layers and attribute types). In these cases, the different files that will be used to create the SDS must be combined in the same .zip format file.
Creating an SDS from vector data files involves the steps of uploading the files to JMap Cloud, analyzing the metadata, validating and completing the SDS parameters. When you complete the creation of the SDS, the data and its configuration are copied into the JMap Cloud databases.
In the case of creating an SDS from raster data files, these are uploaded to JMap Cloud, their characteristics are analyzed and validated and when you complete the creation of the SDS several processes are carried out:
Data is reprojected to the reference coordinate system EPSG:3857
Data is converted to COG optimized format
A pyramid of internal resolution images is created to optimize the display of data
This image, optimized for easy display and navigation, is stored in JMap Cloud.
On the Data sources tab, click on Create a spatial data source.
Select Data file. The selection interface offers two choices: New File, to upload a data file to JMap Cloud and Existing File, to select files that are already on JMap Cloud. See Uploading Files for more information.
If you are creating the data source from a new file, in the New File tab select the data file to upload. Because typically a vector spatial dataset is made up of multiple files, you must combine them into a single .zip format file. Compression is not necessary for uploading raster data files unless you want to upload multiple files that will make up a mosaic dataset. In this case you must combine them in a single .zip format file. If you are creating the data source from files that already exist on JMap Cloud, select them in the Existing File tab.
Configure the SDS settings. When you select a new file, before displaying the settings configuration window JMap Cloud analyzes the file's metadata in order to identify the format, the type of data it contains, it coordinate reference system (CRS), geographic extent and other metadata. When you select an existing file, JMap Cloud has already performed this analysis (and the conversion in the case of raster type files) and the configuration window is displayed directly. The settings to configure vary depending on the data type format. The File settings section details them.
Add a description of the SDS and tags that may be useful for filtering data sources. You can create new labels by entering the text in the Tags field.
Click on Create. The new SDS is displayed in the table. Its status is Preparing while the creation is completed. Subsequently the status is Ready.
The files that you upload when creating an SDS are displayed in the table in the Files tab. After a period of 10 days the files are automatically deleted from JMap Cloud.
The table shows the general settings to configure when creating an SDS from files.
Name
Give the SDS a name. There are no restrictions for the name of resources (SDS, projects, map layers) in JMap Cloud.
Layer
Vector data only. This setting is specific to files that contain multiple data layers (GML, DWG, GeoJSON, etc.). Select the layer from which you are creating the SDS.
CRS
If JMap Cloud has correctly identified the CRS, this field cannot be modified. Otherwise, select the data projection system.
X
Vector data only. This setting is specific to CSV format files. Select the field (numeric values) that contains the latitude coordinates.
Y
Vector data only. This setting is specific to CSV format files. Select the field (numeric values) that contains the longitude coordinates.
Unique identifier
Optional. Vector data only. Select the field that contains the unique identifier of each map element. This identifier is necessary when you want to establish links with other data sources.
Attributes
Vector data only. File attributes are presented in a table that contains the attribute name and type as well as a box to check which attributes should be indexed.
Description
Optional. You can add a description of the data source.
Tags
Optional. You can add labels that can be used to sort or filter SDS. Tags are available for use with all resources (SDS, projects, layers).
Only indexed attributes can be used in simple searches (searching for features in layers of a project based on attribute values) of the NG map application.
Coming soon.
Coming soon.
You can create spatial data sources (SDS) from four types of data sources:
Vector or raster data files: different formats are supported (SHP, CSV, GML, GeoJSON, FileGeoDB, GeoPackage, DWG, Tab, GeoTIFF).
WMS/WMTS Services
Vector Tiling Services
Feature Services
The Data sources tab contains functions for creating and managing spatial data sources that you will use in your projects.
This section presents a table of the SDS of which you are the owner and the sources of the data for which you have access permissions. See the Permissions section for details on access and management of resources.
Each data source is a row in the table, and the columns show the attributes: source type, status, CRS (coordinate reference system), labels, and last modification date.
To create a SDS click on Create a spatial data source. The drop-down menu allows you to select the source type: Data File, WMS/WMTS Service, Vector Tile Service, Feature Service.
The following steps depend on the type of data source.
The dashboard is the home section of JMap Cloud Portal. As its name suggests, this section offers an overview of the status of resources such as projects and spatial data sources and also allows you to create some of them directly.
1
2
The Spatial Data Sources card displays the number of data sources to which you have access, either because you are the owner or because you have access permissions.
3
Usage displays the organization's data volume. Only members with the Administrator role see this card.
4
This section allows you to give a name to the organization and copy the organization's unique identifier to access JMap Cloud Portal.
Write the name of the organization in the Name field.
Click on if you want to copy your organization ID to the clipboard for use in another context.
The unique organization identifier is used by external systems and platforms to connect to JMap Cloud. JMap Server, for example, uses this ID to connect to JMap Cloud. The JMap Server Administrator's Manual provides details on this topic.
Web Map Service (WMS) and Web Map Tile Service (WMTS) are two standards proposed by the Open Geospatial Consortium (OGC) that determine how client applications should make requests to obtain maps from a server compatible with WMS or WMTS respectively.
WMS-compatible servers use the HTTP protocol and the returned maps are usually images in popular formats (PNG, GIF, JPEG, etc.). WMS server capabilities are published in an XML document that specifies the types of queries supported as well as metadata (lists of layers, supported projections, etc.).
WMTS-compatible servers allow you to obtain map data in the form of predefined tiles from a data server.
JMap Cloud can query servers compatible with both standards in order to create spatial data sources.
The settings you need to complete are as follows:
Name
Give the SDS a name. There are no restrictions for the name of resources (SDS, projects, map layers) in JMap Cloud.
GetCapabilities URL
Enter the GetCapabilities URL which will return the capabilities of the WMS or WMTS server. The URL must use the https:// protocol, otherwise an error message is displayed. The URL should look like this: For a WMS compatible server: https://www.server.com/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities
For a WMTS compatible server:
Description
Optional. You can add a description of the data source.
Tags
Optional. You can add labels that can be used to sort or filter SDS. Tags are available for use with all resources (SDS, projects, layers).
The Projects card displays the number of projects to which you have access, either because you are the owner or because you have access permissions. You can create a new project by pressing .
The API Keys card displays the number of API keys configured by your organization. Only members with the Administrator role see this card. You can create a new API key by clicking on .
This section allows you to create and send invitations to members of your organization to join JMap Cloud Portal.
A table displaying the invitations that were made from this tab or from the Members tab, detailing for each their identifier, the email address of the member who sent the invitation, the email address of the invited, the creation and expiration dates of the invitation. The menu displayed at the far right of the row of each invitation provides access to functions such as view information and delete the invitation.
The menu displayed in the header of each attribute in the table allows you to sort the invitations, filter them, hide or show the attributes.
This is the function of the tab. To invite a member:
Click on + Invite member.
Provide the email address, select the role you are assigning to the guest member from the drop-down menu and select the language of correspondence.
Click on Create. An interface appears indicating that the email has been sent and allowing you to copy the invitation link to the clipboard.
If you want to copy the invitation link to the clipboard, click on .
Close the window. The invitation appears in the invitations table.
Click on to view the options: Display Info, Delete.
Click on Display info. The Invitation window opens displaying the email address of the invitee, the email address of the member who created the invitation, the invitation creation and expiration dates, the language of correspondence, the assigned role to the guest as well as the invitation link, which you can copy to the clipboard.
Click on Delete to remove the JMap Cloud Portal invitation link. The invited member can no longer use the link to access it.
The invited member receives an email from JMap Cloud inviting them to join the organization in JMap Cloud Portal.
In addition to displaying the name of the member who created the invitation, the email shows the invited member's email, organization name, and invitation link. An Accept Invitation hyperlink also appears at the end of the message.
If the invited member has the Administrator or Editor role, he accesses JMap Cloud Portal. If he has the Viewer role, once connected he accesses, via the JMap NG cartographic application, the projects for which he has access permissions.
The invited member can then click on the invitation link or the Accept invitation hyperlink to open the login interface Accept invitation to register | Portal that allows them to select a password .
The table presents the different statuses that can have a spatial data source.
Uploading
Files only. The file is being uploaded to JMap Cloud.
Analyzing
Files only. The file is being analyzed. JMap Cloud detects file characteristics such as file type, CRS, attributes, etc.
Analyzed
Files only. The file has been analyzed and its characteristics must be validated by you.
Preparing
Files only. Once the file characteristics have been validated and the data source parameters have been completed, the data is loaded into the JMap Cloud databases.
Processing
The data source is being updated.
Ready
The spatial data source is ready to use.
Error
Indicates an error in one of the steps of creating or updating the SDS.
You can add access permissions to vector and raster spatial data sources (SDS) that you own.
You can grant permissions to members of your organization who hold the Editor and Viewer roles. Each role has different permissions.
Editor
Owner
This permission, the broadest, allows the user to:
grant access permissions to members of the organization,
delete the SDS.
The SDS must have at least one owner.
Editor
Modify
This permission allows the user to modify the SDS settings.
Viewer
View
For the user with the VIEWER role, this permission, combined with the Extract Features permission, allows the user to view SDS data in a cartographic application (such as JMap NG). For a user with the EDITOR role, this permission allows the use to view the SDS in JMap Cloud Portal and use it in projects.
Viewer
Extract Features This permission allows the user to extract features from the SDS and, combined with the View permission, allows to view SDS data in a cartographic application (such as JMap NG).
Viewer
Create Features This permission allows the user to create features in the SDS in a cartographic application (such as JMap NG).
Viewer
Edit Geometries This permission allows the user to edit the geometry of SDS features in a cartographic application (such as JMap NG)
Viewer
Edit Attributes This permission allows the user to edit the attributes of SDS features in a cartographic application (such as JMap NG).
Viewer
Delete Features This permission allows the user to delete features of the SDS in a cartographic application (such as JMap NG).
Permissions are hierarchical:
Owner permission includes Modify and View permissions
Modify permission includes View permission
The permissions associated with the Viewer role are the basis of the hierarchy and each of them automatically includes the View permission.
To grant permissions to a SDS:
Click on and then on Permissions. The permissions configuration interface opens displaying the members with the permissions each has.
To grant permissions to a member, open the Add member drop-down list.
Select the member you are interested in. Their name along with a letter that indicates their role appears in the Add member field. You can clear the selection by clicking .
Select the other members you want to add, one at a time. Their names appear in the Add member field. You can clear the selection by pressing .
Once members are selected, click on to add the members. These are displayed in the permissions table.
Check the permissions you want to grant to each member.
You can modify the permissions granted to members, grant permissions to new members, or remove all permissions from one or more members.
SDS must have at least one member with the Owner permission.
Change the permissions by checking or unchecking the relevant boxes. Résultat de traduction
To remove all permissions from a member, you must first uncheck the permissions at the top of the hierarchy. When you uncheck the Owner permission box, Modify automatically becomes the most important permission. To remove the View permission when associated with Viewer type permissions, you must uncheck those first.
This section displays a table of organization members as well as a button to invite new members to JMap Cloud Portal.
For each member, the table displays the name, username and email address. The menu displayed at the far right of each member's line provides access to functions such as displaying the member's information, modifying it or even deleting the member.
The menu displayed in the header of each table attribute allows you to sort the members, filter them, hide or display attributes.
To add a member to the organization:
Click on Invite Member.
Enter the email address of the person to invite.
Select the person's role from the drop-down list.
Select the correspondence language.
Click on Create. A message appears indicating that an email has been sent to the person. You also have the option to copy the invitation link.
Click on to copy the invitation link to the clipboard.
Close the window. The invitation appears in the Invitations tab.
Click on to display options: View information, Edit, Delete.
Click on Display info. The Member window opens displaying the member's name, email, and role.
Click on Edit. The Invitations window opens displaying the member's name, email, and role. The attribute you can modify is Role.
Select a role from the drop-down list.
Save the change. The role is updated and the window closes automatically.
Click on Delete. This action has impacts on resources that belong to the member, as detailed in the following section.
Organization members who hold the Administrator or Editor role own resources such as files, data sources, and projects with its layers.
When an Administrator or Editor member is deleted, the administrator must decide the fate of the resources belonging to him.
Press Delete, the following message is displayed.
Check the Transfer ownership to field and select the member from the drop-down list if you want to transfer ownership of the resources to another member.
Click on Delete. The deleted member's permissions (access control list entries, ACLs) are removed. The designated member is registered as the owner of the resources that belonged to the deleted member.
You can also click on Delete directly, without transferring ownership of the resources. The member and the resources (with their dependencies) belonging to it are deleted. The member's permissions (access control list entries, ACLs) are removed.
Deleting a member means that they can no longer connect to JMap Cloud Portal.
Deleting a member is irreversible because they are physically deleted from the organization's identity manager.
Click on and then on Permissions. The permissions configuration interface opens displaying the members with the permissions each has.
If you want to remove members, select them by checking the box to the left of each name and press .
You can edit data from a vector spatial data source. The procedure allows you to modify the file or web service that provides spatial data to the SDS.
Select Update data to open the interface which allows you to select a new file or an already existing file in JMap Cloud or, in the case of a web service, to reconfigure the connection request to the service. If the file is not a recognized vector file, the file is refused and this message is displayed: This file is not compatible with the data source. The current SDS name, SCR, description and labels are displayed in the interface and you can keep them as is or change them. The attributes of the new file are displayed, and you can index attributes for easier searches. You must complete certain settings, depending on the file format. The settings are detailed in the section. A new spatial table is created with the new data, and the new table is associated with the existing data source. The old spatial table is deleted.
Save. When the changes are completed the status of the SDS becomes Ready. If the SCR of the new file is not the same as the SCR you selected for the SDS, the data is not displayed in the map when you press Display Info.
The new vector data file may differ from the original file in format, SCR, geometries and attributes. In this case you need to update the configurations of the map layers that handle the SDS data.
To display and edit SDS information:
Select Display information. The interface displays SDS data in a map that you can navigate. The dotted box indicates the extent of the data source. The base map comes from OpenStreetMap. The elements of the SDS are progressively loaded into the map up to a maximum of 50,000 elements. When the maximum number is reached, the other elements are not loaded. Digital elevation models (DEMs) from geoTIFF files are displayed in shades of gray. Other parameters displayed are: the unique identifier of the SDS in JMap Cloud, the coordinate reference system (CRS), the number of elements loaded, tags, description and a table with attributes.
Click on to copy the unique identifier of the data source to the clipboard.
When you hover over the Description, Tags, Unique identifier settings as well as Indexed heading of the attribute table , the icon is displayed allowing setting edition.
Click on or on to save or discard changes.
Only indexed attributes can be used in simple searches (searching for features in layers of a project based on attribute values) of the NG map application.
To delete an SDS:
Click on Delete. A message asks you to validate your choice.
Press OK to delete the spatial data source. All the SDS configuration is deleted.
The data file from which the SDS was created is not deleted and remains in the Files tab for a period of 10 days.
You can upload files to JMap Cloud to later use them to create spatial data sources. The Files tab in the Spatial data Sources section provides functionality for uploading and managing files.
Data from the files you upload is stored in JMap Cloud databases. Files in the Files table are automatically deleted after a period of 10 days.
This tab shows a table of files you have uploaded. A button allows you to upload new files.
The table contains the file name, file data type (vector or raster), format (CSV, KML, DXF, DWG, SHP, TAB, GeoPackage, FileGeoDatabase, GeoJSON, GeoTIFF), size, status and the date of upload. Multiple files can have the same name.
You can select one or more files in the table by checking them and the Delete function becomes available. This allows you to delete multiple files at once.
Since a vector spatial dataset typically consists of multiple files, you must combine them into a single file in compressed .zip format.
Compression is not necessary for uploading raster data files, unless you want to upload multiple files that will make up a mosaic, in which case you must combine them into a single .zip format file.
Drag and drop one or more files to upload directly into the board. The upload begins automatically.
OR
Click on Upload file to open the file explorer.
Select the files to upload. The upload begins automatically.
Up to three files are loaded simultaneously.
The maximum file size that can be uploaded is 15 GB.
In both cases, the files are displayed in the table and messages indicate the upload progress.
The status of each file indicates which step of the process was completed by JMap Cloud.
Waiting
The file is waiting to be uploaded.
Processing
The file is being analyzed.
Analyzed
The file has been analyzed by JMap Cloud which identifies properties such as file type, CRS, attributes, etc. It is available to create a spatial data source.
Uploading
The file is being uploaded. A line in the Status column indicates the progress of the upload. A circle in the header bar indicates the progress of the upload as well as the number of files being uploaded. A message indicates whether the uploadt a été effectué avec succès ou s'il y a eu un échec.
Uploaded
The file has been uploaded. It needs to be analyzed to be available for creating a spatial data source.
Error
There is an error in the file loading process.
Like other resources, to manage a file:
Click on Create source. This function is available when the file status is Analyzed. The interface for creating a data source opens.
Enter the information to create the data source. Details are offered in the Data Files section.
Click on Create. The data source is created and displayed in the table on the Data Sources tab.
This function is available when the file is being uploaded or analyzed and allows you to stop the current process.
Click on Display informations. The interface displays the following information: file name, size, format, status, user ID of the user who uploaded it, date and time of upload and metadata. Metadata includes in addition to the above information, the unique identifier of the file, organization and task; the name of the data layers, the name and type of each attribute, the number of elements.
Click on Delete. A message asks you to validate your choice.
The deleted file disappears from the table. The spatial data source created from the file is not affected.
Click on to display the available functions which depend on the status of the file: Create source, Pause upload, Display information, Delete.
Once the data is connected, the next step is to organize it into projects that can be distributed to end users through mapping applications.
A project is composed of an ordered list of layers. A JMap Cloud mapping application opens projects and displays their layers. You can create as many projects as you want.
Each layer of a project is associated with a . The data source provides the layer data. Different projects can contain layers sharing the same data sources, allowing for a variety of styles, information, themes, etc. for displaying the same data. It is also possible for several layers of the same project to share the same data source, using filters.
A project is a secure resource, which means that it has permissions associated with it to control access by end users. It is therefore possible to exercise precise control over which users will be authorized to open each project.
The Projects section of JMap Cloud Portal allows you to create and manage projects. You can also create projects directly from the .
The following sections describe the steps for creating a new project as well as managing the projects you have access to.
To change project settings:
Click on and then on Edit.
Edit the project settings. You can change all settings.
Click on Edit to save the changes. The date of the modification is displayed in the Modification column (in the list view mode).
To open the project to explore it and fine-tune the configuration before making it available to users:
Click on and then on Open. A JMap NG application displaying the project opens in a new tab.
Log in to the application with your JMap Cloud Portal login information.
Navigate the map and explore the app. The functions offered by JMap NG are available (see details in the JMap NG User Guide). It is the cartographic application that broadcasts the project to members whose role is Viewer.
In JMap NG, click on and then Logout to close the application.
You can create a new project from the Dashboard or from the Projects section.
To create a new project:
Click on Create a new project.
Complete the project settings.
The project displays in the Projects section. In both display modes, cardboard or list, the menu offers functions for managing projects.
Name
Enter a name for your new project. As with other JMap Cloud resources, the name does not need to be unique. Press the French button if you want to give the project name in another language (English or Spanish).
Default language
Among the available languages, select the one that will be used by default when the requested language is not available or translations are missing.
Public
Map CRS
Select the map reference coordinate system. It determines how data is displayed in map applications. All data using a different projection is converted on the fly to that projection. The default CRS in JMap Cloud is EPSG:3857 - WGS 84 / Pseudo-Mercator, the most common for web mapping applications.
Map unit
Select the map unit. The mapping unit is automatically selected based on the selected CRS.
Display unit
Select the unit used to display map coordinates.
Measurement CRS
Select the coordinate reference system that will be used for calculating measurements. The default CRS is EPSG:4326 - WGS 84, latitude/longitude coordinate system used by global positioning systems (GPS). Distance and area measurements are made using spherical calculations based on the ellipsoid of the projection.
Measurement unit
Unit used to display measurements (distance, area, etc.).
Background color
Default background color of the map.
Selection color
Color of selected objects on the map. This parameter can also be defined for each layer.
Initial rotation
If you want to print a rotation to the map, enter the rotation value in degrees. The rotation is clockwise.
Description
Optional. Enter a description for the new project. This is useful for project management purposes.
Tags
Optional. Add tags that can be used to sort or filter projects. You can create them by writing the text in the range. Once created, they are available for use in all resources (SDS, projects, layers). They appear when you enter label terms.
Projects that you have created (and of which you are then the owner) as well as projects for which you have access permissions appear in the Projects section.
Two display modes are available in this section: table mode, similar to the display mode of other JMap Cloud Portal resources, or card mode. You can switch between modes by pressing the and icons respectively.
When projects are displayed in list mode you can sort and filter them based on their name or modification date.
The Menu available in both display modes offers functions for managing each project: Open, Edit, Permissions, Get the project's public link, MVT cache, Delete. The following sections describe these functions in detail.
When the visibility of a project is Public, users access the project without the need for authentication. When