Skip to main content

Map Layer Server concepts

Abbreviations​

Table 1-1 Abbreviations

AbbreviationTerm
3DThree-dimensional (as in 3D objects and vector maps)
APIApplication Programming Interface
CACertification Authority
CPUCentral Processing Unit
CRSCoordinate Reference System
DNSDomain Name System
DTMDigital Terrain Maps
EPSGEuropean Petroleum Survey Group (name of geodetic systems public registry)
ESRIEnvironmental Systems Research Institute (name of geodetic systems public registry)
GISGeographic Information System
GPUGraphic Processor Unit
GUIGraphical User Interface
HTMLHyperText Markup Language
HTTPHypertext Transfer Protocol
IDIdentifier
IPInternet Protocol
JSONJavaScript Object Notation
KMLKeyhole Markup Language
MCMapCore
MSIMicrosoft Installer
OGCOpen Geospatial Consortium
OSOperation System
PEMPrivacy Enhanced Mail
RAMRandom-Access Memory
RPMRed Hat Package Manager file
SaaSSoftware as Service (Windows)
SDKSoftware Development Kit
SRIDSpatial Reference Identifier
URIUniform Resource Identifier
URLUniform Resource Locator
UTMUniversal Transverse Mercator
WMTSWeb Map Tile Service
XMLExtensible Markup Language

Glossary​

Table 1-2 Glossary

TermDescription
AdministratorIT specialist allowed to Install and configure the mapping server.
Client applicationAn application that uses MapCore™ Map Layer Server to get mapping data.
Data repositoryMapCore™ Map Layer Server folder where all layer data and other customized data resides. Refer to Server Execution Parameters for a detailed description
GroupThe group is a logical entity used by the server to present layers together. Refer to Group for a detailed description.
LayerMapping materials that contain observable, geo-positioned information, stored on MapCore™ Map Layer Server; refer to Layer for a detailed description.
OperatorA specialist managing the MapCore™ Map Layer Server content.
PackageMapping materials arranged to be uploaded to the server; refer to Package Descriptor for a detailed description.
Server execution parametersSet of parameters that may be defined when starting the MapCore™ Map Layer Server. Refer to Server Execution Parameters for a detailed description.
Silent importNon-GUI manual background process of uploading new layers to the MapCore™ Map Layer Server.
Source coordinate systemRelevant only for cases of coordinate system conversion between the input coordinate data by which the layer data may be interpreted and a different coordinate system. In such cases, the input coordinate data is called source coordinate system Refer to Coordinate System for detailed information.
Target coordinate systemThis is the coordinate system used by MapCore™ Map Layer Server when importing and previewing the layer. Refer to Coordinate System for detailed information.

Basic Concepts​

The following concepts are used throughout this documentation. Depending on the action(s) taken, some concepts may apply while others do not.

Default Installation Folder​

This is the folder to which the MapCore™ Map Layer Server is installed by default. By default, it contains both the default data repository folder and the default server executable folder. Understanding the structure of the MapCore™ Map Layer Server installation directory is important for proper management of configuration files. Refer to System Folders and Configuration Files for further information.

Default Server Executable Folder​

This is the folder in which the server executable resides by default and from which the server is started. It is also the folder in which the server configuration file McMapLayersServerConfig.xml resides by default, unless the server execution parameters name another one, as the Windows installer and the Linux packages do. Refer to System Folders and Configuration Files for further information.

Default Data Repository Folder​

This is the folder to which the MapCore™ Map Layer Server saves by default all customized user data, including layer data as well as the layer configuration file McLayersDataConfig.xml. In new installations, it is advisable to move the data repository to a customized location. In existing installations that are configured to work with the default data repository folder, the data must be copied temporarily to a different location when updating the server and then copied back to the default data repository folder. Refer to System Folders and Configuration Files for further information.

Server Execution Parameters​

Server execution parameters are a set of parameters defining server execution preferences, including the respective locations of the server configuration file and the layer configuration file. Refer to System Folders and Configuration Files for further information on these files. Refer to Server Execution Parameters for details regarding available parameters and their usage.

Layer​

A layer is a set of geo-referenced mapping data. Each layer in the server’s repository can be previewed via the GUI on its own or together with other layers in a group providing that all layers in the group are of the same area of interest, coordinate system, and tiling scheme. The following table describes the possible layer types.

Table 1-3 Geo-referenced layer types used by MapCore™ Map Layer Server

Layer typeDescription
RasterA layer based on a bitmap of pixels containing rectified image or map. Raster images typically store topographic maps as well as aerial reconnaissance and satellite images.
DTM (Elevation)A form of raster layer. A Digital Terrain Map (DTM) storing altitude data that enables a 3D presentation of the terrain, line of sight calculation, and other relevant terrain height information. Thus, other layers previewed together with the DTM layer can be shown in three dimensions (3D). The DTM layer also allows the client application to perform spatial calculations such as retrieving the altitude of each pixel over the viewed layer
VectorLayer comprising a geographical database that contains a collection of vector-based geographic information system (GIS) data as well as geometries (e.g., text, lines, areas, or points) of geo-referenced entities with various levels of detail. The vector layer may also contain styling information (e.g., instructions on how to render it) as well as additional meta-data (such as names, population, neighborhood, etc.).
S57Vector layer adhering to the standard S-57 for vector layer format and containing multi-layer upgradeable maritime charts. This format comprises a directory tree containing subdirectories and files, where each file contains multiple layers (object classes). All files are fused into a single large chart with predefined layer names, geometries, and the S-57 chart symbology. Parameters used for the S-57 layer type are identical to those used for vector layers with the stipulation that the value of the StylingFormat parameter be S52. Refer to Styling Format for further details on the S52 styling format
3D modelLayer storing a photorealistic 3D model of an entire terrain including buildings, vegetation, and other land coverage. The layer contains both the geometry of that area and its visual appearance. The layer is provided in 3D Tiles format, either as a folder or as a single 3TZ archive file (*.3tz), and is served to client applications as is (static content).
Vector 3D extrusionSpecial vector layer containing outlines and height values of 3D entities, such as buildings, along with styling information. This layer type allows to easily display the 3D representation of a large urban area above the terrain.
MaterialA form of raster layer (code map) whose pixel values are material IDs rather than colors. The server delivers its tiles losslessly so that the codes are preserved.
TraversabilityA form of raster layer (code map) whose pixel values are the number of traversable directions at each location rather than colors. The server delivers its tiles losslessly so that the codes are preserved.

Layer source materials​

Source materials for the layers can be Raw or Native.

  • Raw layers are unprocessed original source files formatted in any supported standard (see Table 1-3 Geo-referenced layer types used by MapCore™ Map Layer Server above). Compared to the native format, they might perform poorly.

  • Native layers comprise raw data which has been converted to a format native to MapCore™ Map Layer Server and therefore optimized for best performance. A native layer may be supplied either as its folder or as a single 3TZ archive file (*.3tz) holding that folder’s contents, in which case the server reads the layer directly from the archive.

note

Vector raw layers are automatically converted to a native format as they are added to the server using an on-the-fly conversion process.

Group​

A group is a container of layers combined under one common name used by the client application to group layers together. It is advisable to group layers with a common area of interest, coordinate system, and tiling scheme so they produce a sensible image when viewed via the GUI. A layer can be a member of several groups.

Refer to Coordinate System for detailed information on the layer’s coordinate system.

Refer to Tiling Scheme for detailed information on the tiling scheme and its relationship to the layer’s coordinate system.

Layer Backlog​

A special system group that is always present, even when the server is empty after a new installation. The Layer Backlog group contains all layers that are not associated with any group. It may thus contain any layer type regardless of its area of interest, coordinate system, etc.

While backlog layers are not visible to the client applications, they may still be managed by an operator through non-GUI server operations (using Restful APIs). Deleting a layer from the Backlog group will delete that layer permanently from the server.

Search Index​

Relevant for the vector layer only, a search index stores organized layer information for a speedier search within the layer. Search indexes are stored in a database that can later be exported and used to search the layer content by a client application.

Styling Format​

Relevant for vector layers only, including S-57 layers. Defines the layer rendering format for these layers. Possible styling formats are:

Table 1-4 Styling formats

Styling formatDescription
NONEIf no styling format us defined, the default MapCore™ schemes are applied, according to the data source geometry.
INTERNALRelevant for KML, KMZ file types only. The data source internal styling is applied.
S52Relevant for S-57 layer type only. S-52 chart symbology is applied.
CUSTOMA folder containing user-defined styling in which XMLs and MapCore™ object schemes must be specified.

Tiling Scheme​

The tiling scheme is the method used to attach map tiles to a geo-positioned, scale-sensitive grid. The tiling scheme parameter comprises both a method for cutting the maps into tiles and the axis origin (in world coordinates) of the tile matrix. A single tiling scheme must be shared by layers in order to preview them together.

The default system tiling scheme is used to display raw layers unless another scheme is specified. For native layers, the designated native layer tiling scheme is set when the native layer is created. The following table details possible tiling schemes:

Table 1-5 Tiling schemes

Tiling schemeDescription
MAPCOREA tiling scheme that was designed by MapCore™ and is thus made for best performance. By default and unless otherwise specified, native formats are created using the MapCore™ tiling scheme. This is also the default tiling scheme in the map layer server unless otherwise configured. NOTE: This tiling scheme is not supported by OGC WMTS; therefore, if the server is used as a WMTS server to non-MapCore™ clients, a different scheme must be specified.
GLOBAL_LOGICALWidely used tiling scheme in most WMTS servers; used mostly in geographical (latitude-longitude) coordinate systems.
GOOGLE_CRS84_QUADA pseudo-Mercator tiling scheme using the WGS84 as its foundation.
GOOGLE_MAPS_COMPATIBLEUsed mainly by Google maps.

The choice of tiling scheme is tightly related to the choice of coordinate system used for the layer:

  • When no coordinate system is provided by the operator and the server is using the coordinate system embedded in the input data, the Default Tiling Scheme parameter is used.

  • When the target coordinate system is provided and it is not specified in the tiling scheme exception table, the Default Tiling Scheme parameter is used.

  • When the source coordinate system is provided and it is additionally specified in the tiling scheme exception table, the tiling scheme defined by the source coordinate system is used.

  • When the target coordinate system is provided and it is additionally specified in the tiling scheme exception table, the tiling scheme defined by the target coordinate system is used.

Refer to TilingSchemePolicy Parameters for details on the DefaultTilingScheme and TilingSchemesByCRS (tiling scheme exception table).

Refer to Coordinate System for details on source and target coordinate system parameters.

Coordinate System​

The coordinate system is a set of parameters required for the import and display of layers in MapCore™ Map Layer Server. MapCore™ Map Layer Server supports all coordinate systems defined by ESPG. Refer to <https://epsg.io/> for more details.

warning

In the absence of such data the layer will fail to upload.

In order for MapCore™ Map Layer Server to present layer data, the EPSG code for the coordinate system used by the layer must be present. The coordinate system used by MapCore™ Map Layer Server to present layer data is called the target coordinate system. For some layer types this is the input coordinate system while for layer types that support conversion between coordinate systems, this is the final coordinate system to be used by MapCore™ Map Layer Server. In the case of coordinate system conversion, the input coordinate system is called source coordinate system. Where no conversion takes place, the source coordinate system is also the target coordinate system.

Depending on the layer type, coordinate system information may be supplied in one of two ways:

  • It may be embedded within the layer data (in which case it is automatically recognized by MapCore™ Map Layer Server); or

  • It may (or is required to) be supplied by the user.

For native layers, the coordinate system is embedded within the data.

For some raw layer types, the information embedded within the layer data may be manually overridden through designated MapCore™ Map Layer Server parameters (see RawLayerInfo Parameters).

Assumptions, options, and requirements related to the coordinate system parameters are detailed in the following table:

Table 1-6 Source and target coordinate system

Layer typeSource coordinate systemTarget coordinate system
RasterEmbedded in input data or manually supplied in layer configuration data.None may be supplied as coordinate system for this layer type cannot be converted by MapCore™ Map Layer Server.
DTMEmbedded in input data or manually supplied in layer configuration data.None may be supplied as coordinate system for this layer type cannot be converted by MapCore™ Map Layer Server.
VectorEmbedded in input data or manually supplied in layer configuration data.Optionally supplied in layer configuration data.
S-57Embedded in input data (cannot be supplied manually).Optionally supplied in layer configuration data.
3D model:
3D TilesEmbedded in input data (cannot be supplied manually).Not applicable. The model is served as is (static content); a target coordinate system supplied in the layer configuration data is ignored. **
3D vector extrusionEmbedded in input data or manually supplied in layer configuration data.Optionally supplied in layer configuration data.

Map Unit​

The size of the map unit varies based on the type of coordinate system (see Coordinate System above) used:

  • In the metric coordinate system, the map unit equals 1 meter, the x and y coordinates equal the specified value, and the z coordinates (height) are always in meters.

  • In the geographic coordinate system, where the x and y coordinates represent longitude and latitude respectively, the map unit equals 1 degree multiplied by 100000. the z coordinates (height) are always in meters.

Verified against MapCore 12.5.0