In every NET Cloud project, layers play a central role. Just like on the GeoServer, the project data is divided into layers. Each layer contains data that originates from the corresponding table of the source data. Thus, each layer contains only data of a specific object type (buildings, joints, documents, etc.).
Important:
What is displayed in a NET Cloud project depends on the layers that are included in the project and their settings.
Within a project, layers can be connected from different sources, including GeoServer, map services, and other services that provide GIS data in WFS or WMS format.
In the detail view of a project, the “Layers” tab provides an overview of all layers available in the project.
Layer Settings
| Layer property | Explanation | Notes |
| Name |
Layer name Layers that are connected via a GeoServer must have the name Background maps from public providers usually have their own name. |
For the name, use only lowercase letters and _ . No hyphens or capital letters if a PostgreSQL database is used. |
| Titel | Visible for labeling in the map legend and when clicking on a feature | |
| SRID | ID of the coordinate system |
Each layer with geoinformation must be specified in the coordinate system EPSG:4326. (Domain) layers without geometry use EPSG:404000. |
| Layer type | Defines the type of data source |
|
| GS layer type | Geometry type of the layer |
Possible settings:
|
| Published | Option whether the layer is displayed on the map | Yes or No |
| Read only | Option whether objects of the layer can be edited | If enabled, no user can create, modify, or delete objects of this layer |
| Option whether the layer is printable | If enabled, a blue printer icon appears next to the layer in the legend (map view) Warning: Even unpublished layers can be printed |
|
| Group | Specifies which group the layer belongs to; used only for grouping in the legend | Configurable in the layer settings detail form |
| Order | Defines the position in the legend | |
| Attributes | Specifies the number of attributes in the layer | |
| Edit | Button to edit | Opens the detail form with layer settings |
| Delete | Button to delete |
It is possible to connect multiple layers in one line separated by commas. These are loaded together and thus provide a performance benefit. However, the corresponding styles and rules must also be defined. This method is recommended only for experienced NET Cloud administrators.
Edit project layers
For quick adjustment of layer properties, changes can be made directly in the row entry. Changes made receive a small marker in the upper left corner and must be confirmed via “Save changes” or “Save”.
Using “Edit” in the row entry of a project layer opens the detail form. In the form, the view can be switched between simple and advanced using the slider.
| 1 | The title of the layer can be stored in multiple languages. The translations are preferred depending on the language selected for the application. If entries are incomplete, the default is used. |
| 2 | The slider can be used to set the zoom level range in which the layer is visible on the map. The zoom level can be selected from 0 to 25 and is displayed in the lower left corner of the map. |
| 3 | Determines the order of the layer within the layer group |
| 4 |
Overlay layer “Yes” – layer is displayed as an overlay; all layers with objects |
| 5 |
Attributes Specific attributes are defined for each layer in the project. These can also be adjusted. |
| 6 |
SLD The display of features on the map and in the legend is described using an SLD (Styled Layer Descriptor) file. This special XML schema can be adjusted as required in the integrated editor. |
Advanced layer settings
On the “Edit project layer” page, setting the slider to “Advanced” reveals additional tabs with further settings for the project layer. The information page for the respective layer is also expanded.
Restrict access to project layers
By default, every user who is enabled for the project also has access to every layer. Similar to projects, permissions can be restricted via the ACL (Access Control List) or the organization.
Warning:
If a restriction (via role, user, or organization) is activated and no selection is made, the layer is not enabled for any role, user, or organization.
By default, all restrictions are disabled. Changes must be explicitly saved.