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...
To begin creating a new spatial data source, go to the Spatial data section and click on Create. Certain parameters are common to all data sources, while others are specific to each type of data source.
Note that custom data source types may also exist. These are new types of data sources that are developed for special purposes using the JMap SDK.
The next configuration steps will depend on the data source type you selected. For more information on configuring a specific type of spatial data source, refer to the appropriate section in this manual.
The projection of the data source must be selected to match the projection of the data. If this parameter is not set correctly, the data displayed may be invalid.
At the last stage of creating a spatial data source, the Start update automatically option allows you to initiate the update when you click on Finish.
If you do not select this option, you will have to launch the update manually from the spatial data section in order for your changes to be taken into account.
External attributes for a spatial data source are attributes that are obtained from an external database (external means a database that is separate from the data source itself). The external attributes are added to the list of existing attributes and can thereafter be used like any other attribute in reports, queries, mouseover, thematics, etc.
External attributes are available only for vector spatial data sources that read data from files (shp, mif, tab, dwg, dgn, etc.) and JMap Spatial tables. When working with vector data sources that access data inside existing spatial databases (PostGIS, MySQL Spatial, Oracle Spatial/Locator, etc.), this option is not available. In that case however, it is often easy to include all needed attributes using normal SQL joins with other tables or by creating views.
External attributes are created from the spatial data source creation wizard.
To create an external attribute, choose External attributes in the Attribute section of the wizard. Press Add and choose one of the following two methods: Select fields or SQL query.
Choose this option in order to select one or more fields from a specific database table from which you want to obtain the values. This option is the simplest method, and it allows you to create several attributes at once.
Choose this option to provide an SQL query that will extract the attribute values in the database. This method is more flexible, but limits you to creating one attribute at a time.
Spatial data sources (SDS) can be shared in order to be accessed by other JMap Server instances. This way, data can be stored in a single location but is accessible from several JMap Server instances.
In JMap Admin, you can share a spatial data source by granting the Remote access permission to one or more users on this spatial data source. This choice must be consistent with the user who established the connection from the JMap Server that must access the shared spatial data sources.
Refer to sections Spatial Data Source Permissions and JMap Server to JMap Server Connections for more information on this topic.
Once a spatial data source has been shared, a icon displays in the list of data sources, in the Shared column.
You can share a SDS with JMap Cloud, a cloud based platform developed by K2 Geospatial.
You must first connect to JMap Cloud. The JMap Server Settings section provides details on this topic. If this step is not completed, a message indicates it in the JMap Cloud section of the SDS configuration interface.
To share or synchronize the SDS with JMap Cloud, in the configuration interface of the SDS, in the JMap Cloud section:
Press Synchronize with JMap Cloud. A window opens and offers you several options:
Copy: A copy of the SDS (data and configuration) is created in JMap Cloud. No link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data will not be synched with JMap Cloud.
Copy and synchronize manually: A copy of the SDS (data and configuration) is created in JMap Cloud. A link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data is not synched automatically with JMap Cloud. You must click on to launch an update.
Copy and synchronize automatically: A copy of the SDS (data and configuration) is created in JMap Cloud. A link JMap Server → JMap Cloud is created. If an update occurs on JMap Server, the data is synched automatically with JMap Cloud. You can also click on to launch an update.
Select one option and press OK. When the SDS is synchronized with JMap Cloud, the JMap Cloud section presents the following information:
Id: The JMap Cloud spatial data source ID.
Status: The current spatial data source status. While synching, this show the current sync task. Otherwise, it shows the JMap Cloud spatial data source status.
Last update: The last time that the spatial data source was synched.
Automatic synchronization: If ON and an update occurs on JMap Server, the data will be synched automatically with JMap Cloud.
Once a spatial data source has been synched, a icon displays in the list of data sources, in the JMap Cloud column.
Press to remove the JMap Server → JMap Cloud link for the SDS. It will not be possible to manually or automatically sync this spatial data source. The spatial data source in JMap cloud is not deleted.
Press to start synchronizing the SDS with JMap Cloud.
Metadata can be associated with spatial data sources in JMap. It can include information such as the person who produced the data, the date it was updated, a description, etc. Users can view this information for the corresponding layers in JMap applications. Metadata can be entered directly into JMap Admin using preset templates or it can be taken from an external metadata management system. Refer to the Metadata Templates section for more information on creating templates.
To access the metadata settings of a spatial data source, click on Metadata in the details section of a spatial data source. The following options are available:
Layers whose data originates from spatial data sources with metadata will automatically inherit this metadata. Metadata can be viewed by users of JMap Web, JMap NG and JMap Pro applications.
Identification
Name
Enter a name for the new spatial data source.
The name must be unique.
Type
Select the type of data source that matches the type of the data to read.
All supported data source types are shown in the list.
You can also search the list by typing a few letters in the search field.
Description
Optionally enter a description for the new spatial data source.
This description can only be viewed by the JMap administrator.
Projections
Original projection
The projection or spatial coordinate system of the data in the data source.
Database
Select the database from which the attribute values will be taken.
This database must already be configured in JMap Admin.
Schema
Select the schema containing the table.
Table
Select the table containing the fields to be used as external attributes.
Include
The list of available fields is displayed.
Select the ones to be included as external attributes.
Get value from
Indicate the name of the field.
Attribute name
You can give the external attribute a name that will be different from the field name.
Dynamic attribute
Select this option if you want the attribute to be dynamic.
Dynamic attributes are read directly from the source in a dynamic manner.
Attributes that are not dynamic are imported into JMap’s system database and are only reread when the data source is updated.
In certain cases, dynamic attributes can reduce the system’s performance.
Join on fields
Select the parameters of the join between the external data and the JMap data source.
Aggregation type
This option is only available if a single field is selected.
Select the aggregation method to use if more than one value is found for the same geometry: Keep first element: Keep only the first value found. Average: Calculate the average value to use as the attribute value. Only available for numeric attributes. Summation: Calculate the summation value to use as the attribute value. Only available for numeric attributes. Using separator: Build a string containing all values separated by the specified character. Only available for text attributes.
Attribute name
Enter a name for the external attribute.
Dynamic attribute
Select this option to make the attribute dynamic.
Dynamic attributes are read directly from the source in a dynamic manner.
Non dynamic attributes are imported in JMap’s System database and are only reread when the spatial data source is updated in JMap Admin.
Dynamic attributes can impact performances in some situations.
Database
Select the database from which the attribute values will be taken.
This database must already be configured in JMap Admin.
SQL query
Enter the SQL query to be executed in the external database that returns the values to use for the external attribute, along with the field used to join with the data source.
Press Execute to test the query and to initialize the other parts of the interface.
Get value from
Select the table and the field to get the values from.
Only those returned by the SQL query are available.
Join on fields
Select the parameters of the join between the external data and the JMap data source.
Aggregation type
Select the aggregation method to use if more than one value is found for the same geometry: Keep first element: Keep only the first value found. Average: Calculate the average value to use as the attribute value. Only available for numeric attributes. Summation: Calculate the summation value to use as the attribute value. Only available for numeric attributes. Using separator: Build a string containing all values separated by the specified character. Only available for text attributes.
Type
3 options are possible: None: No metadata is associated with this data source. External: The metadata comes from a metadata management system that is outside of JMap and accessed through a URL. The URL must be entered in the URL field below. Template: The metadata is entered directly in this section using the selected template.
URL
If the type of metadata is external, this setting defines the URL to be opened in order to view the metadata associated with this spatial data source.
Template
If the type of metadata is template, select the template to be used for this data source.
The metadata entry form for this template displays.
Enter the metadata in the various fields.
JMap Server connects to spatial data by creating spatial data sources (SDS).
Spatial data sources are separated into 2 families: vector data sources and raster data sources. Vector data sources provide vector spatial data along with its attributes, and raster data sources provide raster data (images).
Configuring data sources is usually the first step to publishing spatial data with JMap.
JMap Server connects to spatial data stored in files of various formats (e.g. MID files, SHAPE files, image files, JPEG photo files, etc.) using specific file readers. JMap Server also connects directly to data stored on spatial data servers (e.g. PostGIS, Oracle Spatial/Locator, ArcSDE, WMS/WFS servers, etc.).
Once a spatial data source is created, it must be updated before it can be used. Updating a spatial data source means preparing it for use by JMap Server. This section offers more details on this topic.
The Spatial Data section in Resources displays a table that shows the spatial data sources configured in the server. In this section you can create a new SDS, access the configuration interface of an SDS by clicking on its name, and manage the SDSs you select in the table.
The tasks presented in this section can be performed from the configuration interface of a particular SDS or from the Spatial Data section, by selecting one or more SDSs in the table.
Before a spatial data source can be used to create layers, it must be updated. In JMap, updating a data source generally involves collecting information on the spatial data and its attributes and preparing data for fast and efficient access. This process may be very brief or may take several minutes, depending on the type of data source and amount of data.
In concrete terms, this operation involves different tasks, depending on the type of data source. Generally speaking, for data sources that access data stored in files, the contents are read by JMap Server and inserted in the tables of JMap’s System database. A spatial index is then built for fast access, and attribute statistics are calculated.
For data sources that access data stored on spatial data servers like Oracle Spatial/Locator or WFS systems, the update process is simpler and only involves calculating attribute statistics.
Updating file data sources takes more time than updating server data sources.
You can update several data sources simultaneously. A maximum of three data sources can be updated at a time. Other data sources that need to be updated are placed on hold until their update can be performed.
You can schedule automatic updates for spatial data sources. This action may be helpful if you use data sources that read data files. If the files are frequently modified, you can schedule automatic updates that will occur on a regular basis (every day at midnight, for instance) for the appropriate data sources. Each data source can have its own schedule.
In order to schedule updates for a given data source, click on the icon of the Update schedule from that data source’s details section or select it in the table of data sources. Afterwards, simply follow the wizard to define the specific moments when the updates will take place. Scheduling options are very flexible.
Once these tasks have been scheduled, you can view the current schedule for a data source by viewing its information section.
At any time, you can access the list of all planned updates for data sources by clicking on Scheduler in the Tools section.
When a data source has been deleted, its entire configuration is permanently deleted. The data itself (the file or database) is not affected.
Each spatial data source has a status. The status indicates the condition of the data source, i.e. if it is ready to be used, if an error occurred, etc.
The status of a newly created data source is always set to not ready (unless you checked the auto-update flag). This means that the data source cannot be used yet. In order to be used, every data source must be updated at least once.
Data sources can be updated in batches. A maximum of 3 data sources can be updated simultaneously. Other data sources to be updated are queued until they can be updated.
The following table describes the possible statuses of a spatial data source:
JMap Server can read CSV files or any text file with separated values that contain x and y coordinates. These coordinates can be used for layers of points. The first row must contain the field names. The allowed separators are commas (,), semicolons (;) and tab characters. Text fields may or may not be inside double quotes. X and Y coordinates must be numeric values.
Statuses
Error
An error occurred. The data source cannot handle requests. See error message to determine the source of the error.
Job queued
The data source is waiting to be updated.
A maximum of 3 data sources can be updated simultaneously.
The data source can still handle requests if it was updated at least once before.
Update needed
The configuration of the data source has been modified and it must be updated before the changes are effective.
The data source can still handle requests.
Not ready
The data source is not ready to handle requests.
This status is typically attributed to a data source that has just been created but has not yet been updated.
Ready
The data source is ready to handle requests.
Updating
The data source is being updated.
Depending on the type of data source and volume of data, the update process can be very fast or it can take a certain amount of time.
The data source can still handle requests if it was updated at least once before.
Read | Yes |
Write | No |
Selected files | Select one or more CSV files to read. If selecting more than one file, all files must have the same list of attributes. |
Separator | Select the separator used in the files to read. |
Data type | Select the appropriate data type for each field. |
X field | Select the field that contains the X values. Only numeric fields are listed. |
Y field | Select the field that contains the Y values. Only numeric fields are listed. |
The spatial data source (SDS) configuration interface allows you to access information on a source as well as parameter configuration functions such as metadata, permissions, and attributes.
In the case of raster SDS created from the GDAL library, the configuration interface allows you to add reference coordinate systems to the original projection system of the data. The GDAL - Geospatial Data Abstraction Library section provides details on this topic.
The attribute configuration window contains two tabs: Metadata and Attribute sample.
The Attribute sample tab displays the value of the attribute for a sample of SDS elements.
JMap Server can read ADF and E00 files as a spatial data source. These files are normally produced by ESRI’s Arc/Info software.
JMap Server can read DWG and DXF files produced by Autodesk Autocad versions 12 to 2018 as a spatial data source. Block attributes are read and converted into element attributes.
JMap Server can read DGN version 7 and 8 files as a spatial data source. Select the data source type that is appropriate for your DGN files’ version. DGN files are generally produced by Bentley MicroStation.
DGN files are often paired with a database of attributes. This can be an MS Access database or any other database system. If the DGN files have attributes stored in a separate database, you must first configure a database connection pool for that database before proceeding. See Creating Databases for more information on database connection configuration.
The Permissions button appears in the Spatial data section and is enabled when at least one SDS is selected. It is also displayed in the SDS configuration interface.
This section has two tabs: Permissions and Owners. The owners are the only ones who can manage the administrative permissions for the SDS, manage the list of owners and delete it.
A list of users and groups with permissions appears in the Permissions tab. Click on to add new users or groups.
Available users and groups are configured in the JMap Server section of JMap Admin. Refer to the section for more information about managing users in JMap Server.
Only administrator permissions are associated with spatial data sources.
JMap Server can read ESRI File geodatabases as a spatial data source.
JMap Server can read EDIGEO files as spatial data sources.
JMap Server can connect to databases containing geometries that have been coded according to WKB and WKT standards ().
In addition to the column containing the geometry, you must have a number column with unique integer values used as element identifiers. There must also be 4 columns containing the values of minimum bounding rectangles (MBR).
An SQL query must be provided. The query will be launched to read the data and it can access more than one table at a time.
The connection to the database must already be configured. Refer to the section for more information on this topic.
This button in the Attributes section allows you to update the SDS statistics.
Read
Yes
Write
No
Selected files
Select one or more ADF or E00 files to be read. If you select several files, they must all share the same attributes list.
Layers
Select one or more layers to be included in the data source. The data on other layers will not be read.
Read
Yes
Write
No
Selected files
Select one or more DWG or DXF files to read. If selecting more than one file, all files must have the same list of attributes and geometries must be of the same type.
Source
The Autocad file contains a model space and a paper space. The paper space contains additional elements that are intended for printing. Select the space to use in order for the data to be read by JMap (typically the model space).
Line and polygon options
No conversion: No conversion will be done. Convert closed lines to polygons: Closed line objects will be read as polygons by JMap. Convert polygons to lines: Polygon objects will be read as lines by JMap.
Block reference options
No conversion: No conversion will be done. The different types of objects (lines, polygons, …) will be treated separately by JMap. Convert block references to complex elements: The different types of objects (lines, polygons, annotations…) that compose the blocks will be read together and treated as complex elements by JMap. The maximum size of annotations (texts) is 255 points. The annotations are not displayed at very large scales (zoom too close to the complexes). Convert block references to points: JMap will replace block references by points. This has the effect of considerably reducing the size of the data when the blocks are composed of many objects.
Layers
Select one or more layers to include in the data source. Data on other layers will not be read.
Read
Yes
Write
No
Selected files
Select one or more DGN files to read. If selecting more than one file, all files must have the same list of attributes and geometries must be of the same type.
Convert polygons to lines
Check this option if you want polygons to be read as lines.
Attribute database
Optionally, select the database that contains the attributes. This database must be already configured in JMap Admin.
Layers
Select one or more layers to include in the data source. Data on other layers will not be read.
Read | Yes |
Write | No |
Selected files | Select the directory containing the geodatabase’s structure. |
Layers | Select one or more layers to be included in the data source. The data on other layers will not be read. |
Read | Yes |
Write | No |
Selected files | Select one or more EDIGEO files to be read. If you select several files, they must all share the same attributes list. |
Layers | Select one or more layers to be included in the data source. The data on other layers will not be read. |
Read | Yes |
Write | Yes |
Database | Select the database from which the data must be read. This database must already be configured in JMap Admin. |
SQL query | Enter the SQL query used to extract geometries and attributes from the database. |
Geometry table | Select the physical table containing the geometries. Clicking on Load displays the list of fields returned by the query. This action is required to proceed with the configuration. |
Geometry field | Select the field containing the geometries. |
Geometry type | Select the format of the data to read, either WKB or WKT. |
Encoding (for WKB only) | If the data format is WKB, you must indicate the type of coding used by the data: Little Endian or Big Endian. |
MBR X1 | Minimum X value of the minimum bounding rectangle (MBR) in the geometry. |
MBR Y1 | Minimum Y value of the minimum bounding rectangle (MBR) in the geometry. |
MBR X2 | Maximum X value of the minimum bounding rectangle (MBR) in the geometry. |
MBR Y2 | Maximum Y value of the minimum bounding rectangle (MBR) in the geometry. |
Id field | Select a field that contains unique identifiers. Only the fields containing whole numbers are listed. |
Creation time field | (Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained. |
Modification date field | (Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. |
Author field | (Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained. |
Metadata
Type
Indicates the attribute’s data type.
Dynamic
Indicates whether the attribute is dynamic.
SQL Type
Indicates the SQL type of the attribute data.
Indexed
Check this box to have the attribute indexed.
Title
You can change the title of the attribute.
Format pattern
Specify a format pattern for displaying SDS items.
The pattern must follow the Java standards.
This article offers more details: https://docs.oracle.com/javase/tutorial/i18n/format/decimalFormat.html.
Upon saving, recursively apply to associated layers…
By checking the appropriate boxes, you will apply the title and/or format pattern of the attribute to all layers that are associated with the SDS.
1
General information configured when creating the SDS.
2
SDS parameters configured when it was created.
The hyperlink allows you to access the DB that contains the data.
3
Spatial information.
The extent corresponds to the geographical extent of the elements contained in the SDS.
When it has no elements, the values are equal to 0.
4
Update schedule. Displays scheduled updates for the SDS. Click the icon to set up an automated update.
5
JMap Cloud. This section allows you to share the vector SDS in the JMap Cloud platform.
The section Sharing a vector SDS with JMap Cloud provides details on this function.
6
Attributes. This section presents a list of SDS attributes.
Clicking on the name of an attribute will open a window, allowing you to configure its properties.
7
References. This section lists the projects and layers that use this SDS. A legend indicates which layers are referenced.
8
These buttons allow you to access to the Metadata and Permissions sections, to make the SDS editable (the button only appears for vector SDS), to delete it, update it or edit it.
Remote access | Allows a user to access this spatial data source through a JMap Server to JMap Server connection. This permission must be granted to the user account through which the secure connection between both JMap Servers was established. For more information on this topic, refer to sections and . |
Administrate spatial data source | Allows an administrator to modify the configuration of the spatial data source. |
Access spatial data source | Allows an administrator to create layers that take their data from this data source. |
Vector data sources are used to access vector spatial data (points, lines, polygons, etc.). See the following sections for information on the various types of vector data sources that are supported.
When configuring a vector spatial data source, you need to configure attributes for the data source. All available attributes are listed in a table. By default, all attributes are included but some attributes can be excluded, in which case they will be completely ignored by JMap Server. It is also possible to specify for which attributes JMap Server should create an index in order to optimize performances when queries are performed on these attributes (if no index is used, this will not affect map download and display times). These indexes are used when performing attribute queries on these fields.
This section also contains settings to configure external attributes. See External Attributes for more details on this topic.
JMap Server can read GML files as a spatial data source. GML files must be paired with schema files (.XSD). If a GML file contains instances of more than one feature type, only one of those types can be chosen as the base type for the data source. JMap can read GML files of versions 2.x and 3.x.
This section introduces basic concepts that help you understand how spatial data sources work in JMap Server.
Some spatial data sources support data editing (writing) by JMap Server. This is the case of most DBMS type data sources (PostGIS, Oracle Spatial, etc.). In this manual, each section pertaining to a specific type of data source indicates whether it supports reading only or reading and writing.
File type data sources (SHP, GML, etc.) do not support data editing. However, there is an option allowing you to transform this type of data source into a JMap Spatial data source, which will then allow you to edit spatial and descriptive data in JMap. Once this transformation has been done, the data source will no longer be linked to the original files. All data modifications will have to be performed directly using JMap’s editing tools.
In most data sources that read files, multiple files can be integrated together to form continuous maps. It is frequent for CAD users to split a territory in rectangular tiles. By reading all tile files together, JMap administrators can recreate continuous maps, provided that the files contain the same data structure (geometry, layers and attribute types).
JMap Admin provides a file browser that allows you to navigate through the file system of the server where JMap Server is running in order to select the files to include in the data sources. Local and network storage units can be used, as long as the JMap Server process has access to them.
You can also create user paths. These paths are shortcuts that allow you to save time when browsing the system. They can also be used to write paths that are specific to an operating system, such as Windows UNC (e.g. \myserver\data). To create a user path, you must go to the root of the file system and click on Add user path…
To restrict browsing in the file system, you can define one or more root folders. The JMap administrator will not be able to navigate outside these folders. To do this, you must add a line to the file jmapserver.properties.
Exemple
admin.filebrowser.roots=d:/data1|Data1
In this example, a root folders is created, named Data1.
Accessible through the file browser, the Uploads directory contains files uploaded by all users directly to JMap Server from JMap Admin. If you want to upload a file for use as a spatial data source, click on this folder to access the upload interface.
Enter a name for the file and press Upload. The file will be uploaded to a directory created automatically for your user account. The file is accessible to all user accounts.
System spatial data sources are data sources that are automatically created by JMap to support JMap data source and layer sharing. Normally, these resources do not need to be managed and they are not displayed by default in the list of spatial data sources.
If you wish to display them, you can select Show system data sources in the display settings of the table of the Spatial Data section.
This icon allows you to provide the title in multiple languages.
Key attribute
A key attribute is used when JMap must establish relationships between certain data and your spatial data. It is important to choose an attribute whose values will never change.
If you do not need this parameter, you can keep the default value.
Include
Included attributes are processed by JMap Server.
They can be used in reports, to produce thematic maps, for labeling, etc.
Excluded attributes are totally ignored by JMap Server.
By default, all available attributes are included.
Indexed
JMap Server can create an index on an attribute to speed up queries that will use this attribute.
If you plan to use an attribute for attribute queries, this attribute should be indexed, especially if the data source has a lot of elements.
Read
Yes
Write
No
Selected files
Select a GML file to read.
Feature type
Select the feature type to read. GML files must be accompanied by a schema file (XSD).
GML version
Indicate the version of the GML file (2.x or 3.x).
GPX is an XML-based GPS data exchange format. JMap Server can read GPX files as a spatial data source.
Read
Yes
Write
No
Selected files
Select one or more GPX files to be read. If you select several files, they must all share the same attributes list.
Layers
Select one or more layers to be included in the data source. The data on other layers will not be read.
JMap Server can read shape files as a spatial data source. They are generally produced by ESRI applications.
JMap Server can read GeoJSON files as a spatial data source.
JMap Server can read Industry Foundation Classes (IFC) files as a spatial data source. IFC is the standard exchange format commonly used by software for building information modeling (BIM).
Read
Yes
Write
No
Selected files
Select one or more shape files to read.
If selecting more than one file, all files must have the same list of attributes, and geometries must be of the same type.
Also, each shape file (SHP) must be accompanied by a DBF file and an SHX file.
DBF charset
Select the character set used for the attributes stored in the DBF file.
If this parameter is not set correctly, some characters may not be properly displayed.
The default value is CP437, which is correct most of the time.
Read
Yes
Write
No
Selected files
Select one or more GeoJSON files to be read. If you select several files, they must all share the same attributes list.
Layers
Select one or more layers to be included in the data source. The data on other layers will not be read.
Read | Yes |
Write | No |
JMap Server can read TAB files as spatial data sources. These files are usually produced with MapInfo applications.
Read
Yes
Write
No
Selected files
Select one or more TAB files to read.
If you select several files, they must all have the same attributes list, and the geometries must be of the same type.
Layers
Select one or more layers to be included in the data source.
Data on other layers will not be read.
JMap Server can read KML files as spatial data sources.
Read
Yes
Write
No
Selected files
Select one or more KML files to be read. If you select several files, they must all share the same attributes list.
Layers
Select one or more layers to be included in the data source. The data on other layers will not be read.
JMap Server can read MID/MIF files as a spatial data source. These files are generally produced by MapInfo applications.
Read
Yes
Write
No
Selected files
Select one or more MIF files to read.
If selecting more than one file, all files must have the same list of attributes, and geometries must be of the same type.
Also, each MIF file must be accompanied by a MID file.
JMap Server can read Enterprise geodatabases that use the ArcSDE service (ArcGIS version 10.1 and earlier) to extract spatial and attribute data to be used as a spatial data source. The connection to the ArcSDE service must already be configured. See Creating Databases for more information.
There is a special attribute configuration option that is available only with ArcSDE data sources that have attribute domains.
In order for JMap to use ArcSDE attribute domains, they must be exported into database tables that JMap can understand. There is a tool that plugs into ArcCatalog to create such tables. Please contact K2 Geospatial for more information on this.
Read
Yes
Write
Yes
SDE Connection
Select the SDE connection to use to extract spatial data and attributes. The connection uses the ArcSDE driver and must already be configured in JMap Admin.
Layer
Select the feature class to read. Each table in the SDE database is associated with a different feature class.
Id field
Select the field that contains unique identifiers. Only integer fields are listed. The field is usually called OBJECT_ID.
Creation time field
This parameter is optional. If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field
(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. This field is used to manage transaction conflicts and must be present in the attributes of editable layers for the feature to be enabled.
Author field
(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change.
If no field is selected, the data can still be edited, but this information will not be maintained.
Metadata database
(Optional) This field is used to define the database containing the value domains and the relationships to be used.
These must have been exported from ArcSDE beforehand in a specific table structure.
Attributes
Data source
Select whether the attribute values should be used directly (Attribute) or if they should be substituted by the values specified in the domain (Domain).
JMap Server can connect to any relational database to extract X and Y coordinates that can be used as a spatial data source to create layers of points. The database must contain at least coordinate fields (numeric values) and a field with unique integer values to be used as element identifiers. An SQL query must be provided. This query will be executed to read the data and it can access one or many tables at the same time.
The connection to the database must already be configured. See Creating Databases for more information.
JMap Server can read Enterprise geodatabases from ESRI (ArcGIS 10.0 and later, JMap Server validates the EGDB version) to extract spatial and attribute data to be used as a spatial data source. The connection to the database must already be configured. See Creating Databases for more information.
The spatial data source supports value domains. Relationships defined in the enterprise geodatabase (EGDB) are also supported, but can only be exploited by using external tools.
The data source attributes will correspond to the table columns. To associate the data from other tables, a view can be created in the database and then be configured as a layer in JMap. The data source attributes will then correspond to the columns returned by the view.
JMap has its own storage format for annotations in database tables. If you have any annotations in this format, JMap Server can use them as a spatial data source. Annotation tables in JMap format have a certain number of required fields, as explained in the table below. An SQL query must be provided. The query will be executed to read the data and it can access more than one table at a time.
The database connection must already be configured. Refer to the section for more details on this topic.
Read
Yes
Write
Yes
Database
Select the database to read the data from. It must already be configured in JMap Admin.
SQL query
Enter the SQL query used to extract coordinates and attributes from the database.
Geometry table
Select the physical table that effectively contains the x and y coordinate values. Pressing Load will retrieve the list of fields returned by the query. This action is necessary to configure the rest of the parameters.
X field
Select the field that contains the X values. Only numeric fields are listed.
Y field
Select the field that contains the Y values. Only numeric fields are listed.
Id field
Select a field that contains unique identifiers. Only integer fields are listed.
Creation time field
(Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field
(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained.
Author field
(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained.
Read
Yes
Write
Yes - Only SQL Server supports all CRUD operations (create, read, update and delete). Other databases only support reading.
Database
Select the database connection to be used to extract the spatial data and attributes. The connection is a standard database (Oracle, SQL Server, etc.). It must already be configured in JMap Admin.
System tables schema
Select the database schema where the metadata tables are located.
Schema
Select the database schema in which the table (or view) containing the feature class will be read.
Layer
Select the feature class to be read. Each table in the database corresponds to a different layer.
Id field
Select a field that contains unique identifiers. Only integer fields are listed. The field is usually called OBJECT_ID.
Geometry field
Select the field that contains the geometries.
Creation time field
(Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field
(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. This field is used to manage transaction conflicts. It must be present in the attributes of editable layers in order for the feature to be enabled.
Author field
(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained.
Read | Yes |
Write | No |
Database | Select the database from which the data must be read. This database must already be configured in JMap Admin. |
SQL query | Enter the SQL query used to extract annotations from the database. |
Geometry table | Select the physical table containing the geometries. By clicking on Load, you will obtain the list of fields returned by the query. This action is necessary to configure the remaining parameters. |
X field | Select the field containing the X coordinate of the lower left position of the text. |
Y field | Select the field containing the Y coordinate of the lower left position of the text. |
Id field | Select a field containing unique identifiers. Only fields containing integer numbers are listed. |
Text field | Select the field containing the annotation text. |
Height field | Select the field containing the height of the annotation, indicated in data units. |
Angle field | Select the field containing the rotation angle of the annotation text. The angle is indicated in degrees and increases clockwise. The zero value indicates that the text is horizontal. |
JMap Server can read photo files (360 or normal) in JPEG format as a source of spatial data. These photos can be viewed in JMap Pro and JMap NG applications from point layers associated with this type of data source.
JMap Server reads all image files in the specified directory. Files that are not images or image files without spatial information (latitude and longitude) are ignored.
From each file, JMap Server reads the metadata (latitude, longitude and other information) and writes them to a JMap Spatial table. Coordinates (latitude and longitude) define a point and other metadata are attributes of the point. Direction data can be used, for example, to apply a rotation to symbols that represent the points. 360 photos are processed as normal photos.
Read
Yes
Write
No
Selected folders
Select one or more folders that contain the photos in JPEG format. You can structure the photos into different independent folders to create multiple spatial data sources (e.g. Photos 2020, Photos 2021, etc.).
Reader options
Check the Include subfolders option so that JMap Server read the files stored in the subfolders. Select field labels for geographic coordinates, altitude, and direction.
Attributes
Check the attributes to include in the spatial data source. Select the key attribute corresponding to the unique identifier.
External attributs
You can add external attributes by selecting fields or by using an SQL query. The External Attributes section provides details on adding external attributes.
Projection
Select the original projection of the photos. The photo coordinates are expressed in latitude and longitude, so the projection is Longitude/Latitude (WGS 84) - EPSG: 4326.
JMap Spatial is the format used to store JMap’s spatial and descriptive data. It is based on the WKB format (http://en.wikipedia.org/wiki/Well-known_binary).
An existing JMap Spatial table may be used as a spatial data source or a new one can be created to receive data.
Click on Add table to create a new table in JMap Spatial format. You can also select an existing table and click on Edit table to change its name or structure.
When creating or editing a table, you can add new fields to the table in the User Attributes tab by clicking on and remove fields by clicking on .
A warning message appears if you use an SQL reserved word as an attribute name. You must change the attribute name.
Note that there are other fields in the table displayed on the System Attributes tab. These include geometry fields (vary according to geometry type), spatial index fields, and so on. These fields are created and populated automatically by JMap.
Once the table has been created or modified, it can be used for the spatial data source.
JMap Server can connect to MySQL Spatial databases to extract spatial data and attributes to be used as a spatial data source. The only special requirement is the presence of a numeric column with unique integer values to use as element identifiers. An SQL query must be provided. This query will be executed to read the data and it can access one or many tables at the same time.
The connection to the database must be already configured. See Creating Databases for more information on this topic.
JMap Server can connect to MongoDB to extract spatial data and attributes to be used as a spatial data source.
NoSQL database systems such as MongoDB are widely used in cloud applications. They have made it possible to solve important problems that traditional SQL database management systems have encountered (rigid schemas, lack of scalability, limited performance).
You need to connect to a MongoDB system (https://www.mongodb.com/en) stored locally or in the cloud. MongoDB offers a local application, MongoDB Compass and a web application, MongoDB Atlas that allow you to access data.
The data or documents are organized in collections (analogous to relational database tables) stored in databases that integrate “clusters” (MongoDB deployments). The clusters are organized into projects.
Data loading can take some time due to the lack of structure of the data collections.
JMap Server can connect to ArcGIS Server and ArcGIS Online REST services to access vector data published by this type of service. Geometries and attributes are available, but the other information (styles, scales…) is ignored and must be configured in the layers of the JMap project.
It is also possible to create a JMap project by importing an existing layer configuration from an ArcGIS REST service. Refer to Creating projects for more information.
JMap Server can read ESRI Personal geodatabases to extract spatial and attribute data to be used as a spatial data source. This format uses Microsoft Access files to store the data. The connection to the Access database must already be configured using the MS Access driver. See Creating Databases for more information on this topic.
Read
Yes
Write
Yes
Database
Select the MySQL database to read the data from. It must already be configured in JMap Admin.
SQL query
Enter the SQL query used to extract geometries and attributes from the database.
Geometry table
Select the physical table that contains the geometries. Pressing Load will retrieve the list of fields returned by the query. This action is necessary to configure the rest of the parameters.
Geometry field
Select the field that contains the geometries.
Id field
Select a field that contains unique identifiers. Only integer fields are listed.
Creation time field
(Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained.
Modification date field
(Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained.
Author field
(Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained.
Read
Yes
Write
No
Connection string
Enter the MongoDB cluster connection string that contains your data.
To get the connection string:
1. Sign in to a MongoDB Compass or MongoDB Atlas account.
2. Select the project that contains the data you are interested in.
3. In the section of the cluster that contains the data, press Connect. A window opens for you to select the connection method.
4. Select Connect your application to connect JMap to the MongoDB cluster. A window opens displaying the connection parameters.
5. Press Copy in the connection string range. Instructions for completing the chain are displayed in the window.
6. Paste the connection string in the section Connection string in JMap. You must replace <password> with the cluster password and <dbname> with the name of the database that will be used by default for the connection.
7. Press Load. The connection process may take a few moments.
Database
Select the database in which the data collection is located.
Collection
Select the data collection to connect to.
Id Field
Select the attribute that is considered the JMap identifier of the data.
Projection
Select the original projection of the data.
Read
Yes
Write
No
Read
Yes
Write
Yes
Database
Select the database to read the data from. This database must connect to an MS Access file. It must already be configured in JMap Admin.
SQL query
Enter the SQL query used to extract geometries and attributes from the database.
Geometry table
Select the physical table that effectively contains the geometries. Pressing Load will retrieve the list of fields returned by the query. This is necessary for the rest of the configuration.
Id field
Select a field that contains unique identifiers. Only integer fields are listed. The field is usually called OBJECT_ID.
Raster data sources are used to access raster spatial data (images). See the following sections for information on the various types of raster data sources that are supported
Read
Yes
Write
Yes
Table
Select the JMap Spatial table to be used as a data source. If the table does not exist, you can create it by clicking on Add table.
Web Feature Service (WFS) is a standard proposed by the Open Geospatial Consortium that defines how client applications should request map vector data and attributes from a WFS compatible server. The protocol used is HTTP and the data returned is typically in Geography Markup Language (GML). WFS servers publish their capabilities in an XML document that specifies the types of requests supported and provides a description of available features.
JMap Server can read data from WFS servers versions 1.0.0, 1.1.0 and 2.0 to be used as a spatial data source.
JMap Server can connect to services complying with the OGC API Features standard (https://ogcapi.ogc.org/features/) to use them as spatial data source.
This new OGC standard replaces the WFS services standard.
OGC API Features provides APIs for creating, modifying, and querying “features” (real world elements or entities) on the web.
The OGC API Features is made up of several parts, each of which is a separate standard.
Part 1, the “core”, specifies the basic capabilities and is limited to the recovery of features where the geometries are represented in the WGS 84 longitude/latitude coordinate reference system.
Part 2 specifies capabilities for extracting features whose geometries are represented in all other coordinate reference systems.
Part 3, which is in the development phase, concerns data filtering as well as queries using the Common Query Language (CQL).
Additional capabilities that meet more advanced needs will be specified in additional parts: support for creating and modifying features, more complex data models, multiple data sets, and collection hierarchies (https://www.ogc.org/standards/ogcapi-features).
JMap Server implements part 1 of the standard, which provides access to spatial data (entities or features) organized in collections. The data is sent in HTML or GeoJSON format (https://ogcapi.ogc.org/features/overview.html).
JMap Server can connect to Oracle Spatial or Locator databases to extract spatial data and attributes to be used as a spatial data source. The only special requirement is the presence of a numeric column with unique integer values to be used as element identifiers. An SQL query must be provided. This query will be executed to read the data and it can access one or many tables at the same time.
The connection to the database must already be configured. See for more information.
With this type of data source, it is possible to read ECW or JPG2000 image files or to connect to an ECWP server ( Image Web Server) to obtain images. It is not possible to configure both at the same time.
This type of data can also be read by the GDAL data source with the same performance. This data source is kept for compatibility with existing configurations.
JMap Server can connect to Microsoft SQLServer Spatial databases to extract spatial data and attributes that can be used as a spatial data source. The only special requirement is the presence of a numeric column with unique integer values to be used as element identifiers. An SQL query must be provided. This query will be executed to read the data and it can access one or many tables at the same time.
The connection to the database must be already configured. See for more information.
The projection system selected for the spatial data source must exactly match the spatial reference identifier (SRID, e.g. EPSG) of the elements of the table, for the elements to be displayed.
JMap Server can connect to PostGIS databases to extract spatial data and attributes that can be used as a spatial data source. The only special requirement is the presence of a numeric column with unique integer values to be used as element identifiers. An SQL query must be provided. This query will be executed to read the data and it can access one or many tables at the same time.
The connection to the database must be already configured. See for more information.
Read
Yes
Write
Yes
URL
Enter the GetCapabilities URL that will return the capabilities of the WFS server.
It should be similar to: http://www.server.com/wfs?SERVICE=WFS&VERSION=1.0.0&REQUEST=GetCapabilitie
Feature types
The list of feature types is returned by the WFS server after pressing Load. Select one feature type to read.
Read
Yes
Write
No
Landing page URL
Enter the URL of the service landing page. Press Load to access the service.
Collection
Select the collection (set) of data you want to access.
Page size
The data is sent in pages. Indicate the size of the page, the quantity of features that are sent at a time.
Original projection
Select the original projection of the data: Longitude/Latitude (WGS84) - EPSG: 4326.
Read | Yes |
Write | Yes |
Database | Select the Oracle database to read the data from. It must already be configured in JMap Admin. |
SQL query | Enter the SQL query used to extract geometries and attributes from the database. |
Geometry table | Select the physical table that effectively contains the geometries. Pressing Load will retrieve the list of fields returned by the query. This action is necessary to configure the rest of the parameters. |
Geometry field | Select the field that contains the geometries. |
Id field | Select a field that contains unique identifiers. Only integer fields are listed. |
Creation time field | (Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained. |
Modification date field | (Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. |
Author field | (Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained. |
Selected files | Select one or more ECW or JPG2000 image files to read. If many files are selected, they will be considered as a mosaic. The files must be georeferenced. |
Read | Yes |
Write | Yes |
Database | Select the SQLServer Spatial database to read the data from. It must be already configured in JMap Admin. |
SQL query | Enter the SQL query used to extract geometries and attributes from the database. |
Geometry table | Select the physical table that effectively contains the geometries. Pressing Load will retrieve the list of fields returned by the query. This is necessary for the rest of the configuration. |
Geometry field | Select the field that contains the geometries. |
Id field | Select a field that contains unique identifiers. Only integer fields are listed. |
Automatically convert to valid geometry | When this option is enabled, invalid geometries created in JMap are automatically converted to valid geometries using the SQL function |
Creation time field | (Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained. |
Modification date field | (Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. |
Author field | (Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained. |
Read | Yes |
Write | Yes |
Database | Select the PostGIS database to read the data from. It must already be configured in JMap Admin. |
SQL query | Enter the SQL query used to extract geometries and attributes from the database. |
Geometry table | Select the physical table that effectively contains the geometries. Pressing Load will retrieve the list of fields returned by the query. This is necessary for the rest of the configuration. |
Geometry field | Select the field that contains the geometries. |
Id field | Select a field that contains unique identifiers. Only integer fields are listed. |
Creation time field | (Optional) If you want this data source to be editable by JMap, this field will show the creation date of each object. If no field is selected, the data can still be edited, but this information will not be maintained. |
Modification date field | (Optional) If you want this data source to be editable by JMap, this field will contain the date each object was last modified. If no field is selected, the data can still be edited, but this information will not be maintained. |
Author field | (Optional) If you want this data source to be editable by JMap, this field will either contain the name of the user who created each object or the name of the user who made the last change. If no field is selected, the data can still be edited, but this information will not be maintained. |
JMap Server can use the OpenStreetMap map as a raster data source. No parameters need to be configured for this type of data source.
JMap Server may use a vector spatial data source that comes from another JMap Server instance. To enable this, you must start by configuring a connection towards the other JMap Server. Refer to JMap Server to JMap Server Connections for more information.
JMap Server can connect to ArcGIS Server and ArcGIS Online REST services to access WMTS-type raster data published by this type of service.
Read
Yes
Write
Yes
Remote connection
Select the connection towards another JMap Server instance that must be used to extract spatial data and attributes. The connection must already be configured in JMap Admin.
Data source
Select the existing vector spatial data source on the other JMap Server instance you wish to access. This data source must be shared by the other server.
URL
URL of the service of an ArcGIS REST layer. Exemple http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Demographics/ESRI_Census_USA/MapServer/5
Username
Enter the username to authenticate and log in to the ArcGIS REST service.
Password
Enter the password to authenticate and log in to the ArcGIS REST service.
JMap Server can use a raster spatial data source that comes from another JMap Server instance. To enable this, you must start by configuring a connection towards the other JMap Server. Refer to JMap Server to JMap Server Connections for more information.
Remote connection
Select the connection towards another JMap Server instance that must be used to extract spatial data and attributes. The connection must already be configured in JMap Admin.
Data source
Select the existing raster spatial data source on the other JMap Server instance you wish to access. The data source must be shared by the other server.
Web Map Service (WMS) is a standard proposed by the Open Geospatial Consortium that defines how client applications must request maps from a WMS compatible server. The protocol used is HTTP and the maps returned are typically images in popular formats (PNG, GIF, JPEG, etc.). WMS servers publish their capabilities in an XML document that specifies the types of requests supported as well as the metadata (list of layers, supported projections, etc.).
By configuring WMS data sources, you allow JMap to connect to and query WMS compatible servers (versions 1.0 to 1.3). You can then create raster layers based on these WMS data sources inside projects.
Once you have obtained the capabilities, you can define the parameters for the other types of requests in the WMS protocol. JMap Admin automatically suggests default queries that usually work very well. They are generated from the GetCapabilities request. If you wish to modify these default requests, you must select the Override default request option and enter new requests. For each type of request, you can also activate HTTP authentication and provide sign-on parameters.
Web Map Tile Service (WMTS) is a standard offered by the Open Geospatial Consortium that determines how client applications perform queries to obtain map data in the form of predefined tiles from a data server.
By configuring WMTS data sources, you enable JMap to connect to and query WMTS-compatible servers (version 1.0.0). You can then create raster layers based on WMTS data sources within projects.
This type of spatial data source allows you to read a wide variety of raster data formats. GDAL (Geospatial Data Abstraction Library) is an open source library specializing in raster data conversion and processing.
There can be one or more source image files (mosaic of images). The images of the mosaic can overlap and there can be holes in the mosaic.
When the data source is updated, if the option is activated, a pyramid of lower resolution images is created by JMap Server and stored in the image cache. The image cache is then used for high performance production of images on the fly at specific resolutions. Depending on the initial image sizes and parameters, the image cache size can become voluminous. Typically, the total image cache is about the same size as the original images. Available disk space must be sufficient before updating this data source. It is possible that the data format selected will not require the creation of a pyramid. In this case, the parameter will be ignored.
JMap Server Lima introduces this new feature that allows to select multiple coordinate reference systems for a spatial data source (SDS) created from GDAL. This allows to prepare in advance several versions of the raster SDS in order to offer optimal performances when processing requests from different applications.
Once the SDS is created, the Reprojections section of its configuration interface allows to add (+), update () or delete (
) alternative projection systems to the original one. The table in the section shows the systems configured for the SDS.
When adding a projection system, the SDS is projected into the system and an image pyramid is created and stored in a single file.
When an application uses the SDS, the one projected with the appropriate projection system is used (the projection system must be specified in the parameters of the application's request to JMap Server). For example, JMap NG applications use the EPSG:3857 - WGS 84 / Pseudo-Mercator system, so the SDS projected in this system is used by JMap NG.
If the SDS is not projected in the appropriate system, it is reprojected on the fly which consumes JMap Server resources and compromises the application performance.
Each projection system added to the spatial data source creates a pyramid of images that is stored in a file. You must provide enough storage space for this data.
Get server capabilities (GetCapabilities)
Enter the GetCapabilities URL that will return the WMS server’s capabilities.
The URL should look like this: http://www.server.com/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities
Enable HTTP authentication
Enable this option if the WMS server controls access to the WMS service via HTTP authentication. In this case, enter the username and password that must be used.
Get map(GetMap)
This request is used to get a WMS server map.
Get feature info(GetFeatureInfo)
This request is used to get the attributes of a map element.
URL
Enter the GetCapabilities URL that will return the capabilities of the WMTS server. The URL should be similar to this one: www.server.com/wmts?SERVICE=WMTS&VERSION=1.0.0&REQUEST=GetCapabilities
Press Next to continue configuring the data source.
Original projection
Select the projection of the map data.
Start update automatically
Check this box to automatically update this data source.
Selected files
Select one or more image files to read. You have to select only the files containing the raster data (.tif, .jpg, etc.) and not the additional files (.xml, .prj, etc.). If many files are selected, they will be considered as a mosaic. The files must be georeferenced.
Cache path
The directory where JMap Server will store generated image files for the various resolutions.
Default is JMAP_HOME/cache/raster.
Image interpolation
Method for producing images with reduced resolutions from images with higher resolutions.
Default is Cubic and this method usually produces the best results.
Compute statistics (may take some time)
Statistics on image pixels simplify the analysis of these images. JMap extensions such as JMap Imagery use these statistics to work. Calculating statistics can take several minutes and this option should only be activated when necessary.
If you do not need statistics, do not enable this option.
Create a pyramid
Activates the creation of an image pyramid with several resolutions. This greatly improves performance for producing images on the fly.
Pyramid image interpolation
Method used to produce pyramid images.
The default value is Cubic and this method usually produces the best results.
