In PlexMap there are different layer types, which have influence on the kind of presentation and the loading behavior in the viewer. For example, there are layer types that can only be presented in the 3D viewer or only in the 2D viewer.
PlexMap always tries to find the appropriate Layer for a dataset when creating layers (this depends on the data type, but also on other factors such as the number of elements). However, for the PlexMap user, a basic understanding of layer types is helpful so that Views can be set up optimally (in terms of appearance, loading behavior, and performance).
MapProxy Layers can also consist of combinations of the above mentioned types. For example, it is possible to overlay custom 2D features such as municipality boundaries on top of an existing WMS and create a Layer that contains both datasets rasterized.
All data passing through a MapProxy Layer is cached. This means that they are quickly available when the same tile is called up again and do not have to be queried again from the data source (i.e. WMS service, the database or the GeoTIFF file).
This cache is reset as soon as the Layer is saved again. This happens because the data can change when it is saved again.
By "seeding" is meant the complete caching of an entire Layer. MapProxy is also functional without seeding, but the Seed MapProxy ensures that the individual tiles of a Layer can be delivered without delay.
For MapProxy layers, display and loading zoom levels can be set in the layer settings.
The maximum loading zoom level defines until when a MapProxy layer is loaded. In this zoom level range data is actually reloaded. Normally, a layer should provide data up to at least loading zoom level 20 or 21.
The maximum display zoom level can be set differently from the loading zoom level. Example: A layer was created with loading zoom level 21. If the display zoom level for this layer is set to 24, users can still zoom up to level 24 in the viewer. Although no new data is loaded from zoom level 22 and the display becomes pixelated, a high display zoom level can be useful for measurements, for example.
The minimum loading zoom level defines from which zoom level data should be loaded. If the value is set to 0, data is always loaded. Setting higher values causes the layer to be displayed in the viewer only from a later zoom level. The behavior of the minimum display zoom level is identical. Thus, the minimum display and loading zoom level should be set to the same value.
Note: Defining high loading zoom levels is very memory intensive. So make sure you have enough disk space available and do not set loading zoom levels above 20 for layers that do not have high importance in the viewer.
A layer of type "3D Tiles" contains 3D geometries. For example, it can contain a 3D city model in CityGML format or a 3D mesh that is to be displayed in PlexMap 3D.
Technically, PlexMap uses the OGC standard 3D Tiles, which you can find more information about here.
The layer type "3D Tiles" is suitable for the representation of massive data sets on the Internet. In principle, you can store 3D datasets of any size in the "3D Tiles" layer type and publish them with PlexMap 3D.
The layer type "Address Search", contains address data prepared for the address search in PlexMap. To learn how to correctly prepare address data for address search in PlexMap, see the tutorial "Address Search in Viewer".
The layer type "Billboard (Cesium)", contains billboards for display in PlexMap 3D.
Billboards are, by definition, textured rectangles used in 3D computer graphics to simplify models. They are created by planar projection of the model to be simplified onto a rectangle.
Since this projection breaks down a model that may consist of several thousand polygons to just 2 polygons needed to represent the rectangle, billboards are of interest in the context of PlexMap 3D for performance-optimized web rendering of 3D symbols.
In PlexMap, billboards consist of the simplest possible symbol and a geo-coordinate at which the symbol is to be displayed. You can create billboards in the PlexMap Switchboard using the Billboards from 2D Objects function.
Der Layertyp "Billboard Tiles (Cesium)“, enthält 3D-Texte zur Darstellung in PlexMap 3D (vgl. auch Beschreibung des Layertyps "Billboard (Cesium)“).
In PlexMap bestehen "Billboard Tiles (Cesium)“ aus einem Text und einer Geokoordinate an der Ihr Text angezeigt werden soll. Sie können Billboards im PlexMap Switchboard über die Funktion 3D Text from 2D Objects erzeugen.
The layer type "Spherical panoramas" is used for the preparation of street view images for PlexMap Street360°. A layer of the type "Spherical panoramas" can contain the street panoramas and also possibly point clouds taken in parallel.
To learn how to display "spherical panoramas" in PlexMap 3D, please refer to the tutorial "Publishing 360° road traffic images".
The "Map Service Relay" layer type displays web services (OGC WMTS) from an external server in a PlexMap Viewer (e.g. PlexMap 2D or PlexMap 3D) without storing or caching the service or data of the service in PlexMap (services "looping through").
This can result in improved performance if the external server provides good performance, as external layers always offload the deployed PlexMap server.
The layer type "Universal JSON" is used internally by PlexMap to transfer and store sketches in the context of PlexMap Planner.
Users can publish sketches created in PlexMap Planner as layers for PlexMap 3D using Universal JSON. Compared to the layer type "3D Tiles", "Universal JSON" also supports special planner functions (such as cut-out polygons).
The "WFS" layer type provides a Web Feature Service (WFS) for PlexMap or for external viewers. WFS are fundamentally used to access vector data over the Internet, even if the data is on an external server.
The provided WFS service is loaded in PlexMap tiled. The loading behavior in external viewers depends on the individual configuration of the external viewer.
Wählen Sie einen beliebigen Filter und klicken Sie auf Anwenden, um Ergebnisse zu sehen