[Home] - [Platform Access] - [Admin] - [DDS Config Manager] - [Bulletin: Bulletin Management and Custom Bulletin Editor] - [User Interface and Available Tools] - [Static Layers] -[Observations] - [Forecast Models] - [Events]
Authorized users, typically those with a cross-coordinator or administrative role, can access the DDS Config Manager at the following link:
https://mydewetra3-staging.mydewetra.world/dds-config-manager
DDS Config Manager is the web application used to configure:
The configured resources are consumed by DDS and displayed in Dewetra3.
These guidelines are intended for administrators, configurators and technical users working with data ingestion and visualization.
The DDS Config Manager stores the metadata configuration and uses it to access and publish data.
There are three configuration paths:
There are two group types have different purposes:
| Group | Identified by | Purpose |
| Layer Group | Portal + domain | Controls configuration ownership, visibility, and the scope available to restricted users |
| View Group | Portal + domain + application | Controls where a layer or view is exposed to a specific application, such as Dewetra3 |
For a dynamic layer, assigning a Layer Group is not sufficient to make it visible in Dewetra3. At least one Variable and one Dynamic Layer View must also be configured, and the view must be assigned to the correct View Group.
DDS Config Manager shows different sections (navigation and action buttons) depending on user roles.
| Role | Main GUI capabilities |
| restricted-dds-profiler | Manages Dynamic Layer Views & View Groups (within the user’s authorized portal/domain and the View Groups available to their role) |
| restricted-dynamic-layer-configurator | Manages dynamic/series resources (within the user’s authorized Layer Groups) |
| spatial-aggergations-manager | Manages Spatial Aggregations |
| restricted-static-layer-manager | Manage static-layers (within the user’s authorized Layer Groups) |
| static-layer-publisher | Allows publishing static layers. Typically combined with a static-layer manager role, providing access to the Static Layers screen |
| dds-instance-manager | Manages DDS instances and their credentials |
| sensors_manager | Uses the Sensors Manager |
Restricted roles determine both what the user can see and what the user can modify in the DDS Config Manager:
If a section or action described in this manual is not visible, verify the user’s roles and allowed groups with the portal administrator.
Depending on permissions, the main navigation may include:
Additional resources (such as Styles, Buckets, Layer Groups, View Groups, and Time Aggregations) are opened from selectors inside an editor.
Most list screens in the DDS Config Manager share the same basic controls. These controls allow users to filter, create, edit, clone, delete or view configuration records.
Editor headers share a set of common actions:
Names and Data ID values are unique identifiers. They are normally locked after creation.
To change one, clone the record with the new desired identifier, update all its dependants, verify the new configuration, and only then remove the old record.
Resource selectors allow users to:
This functionality allows you to create missing Styles, Buckets, Groups, or Aggregations without interruping the configuration of the main layer.
The global search allows users to search across all configuration resource types.
How it works:
Global search is useful for quickly locating layers, variables, styles, aggregations, or any other configuration element.
A Dynamic Layer describes a DDS-managed data source. It defines where the configuration is deployed, which DDS component handles it, and the source-specific properties. Variables and Dynamic Layer Views are configured separately.
To create a Dynamic Layer:
| Field | Required | Description |
| Data ID | Yes | Unique DDS identifier for the dataset. It is locked in Edit mode. Use a stable, environment-compatible value and avoid spaces. |
| Instances | Operationally required | DDS deployments that receive or serve this configuration. |
| DDS Component | Yes | Java component used by DDS. New layers default to com.acrotec.data.dds.components.ms.DDSMapComponentMS. |
| Layer Group | Required for scoped operation | Portal/domain ownership and authorization scope. Restricted users must select an allowed group. |
| Properties (JSON) | Source dependent | Data access and layer properties. The value must be a JSON object. It is always filled in automatically. |
When using the default DDS microservice component, the JSON area is read-only. Selecting “Edit” opens a guided dialog, as follows:
| Dialog Field | Meaning |
| data_path | Path or source identifier used by the data service inside the bucket. Confirm its exact value with the data provider. |
| data_shape | Data organization type: forecast, datacube, or observation. |
| data_backend | Backend implementation. For current layer configuratons, use cima_data_lib. |
| secretName | Name of the runtime secret containing the credentials required by the data service. |
Saving the dialog automatically creates the structured repo_info and ms_name properties expected by the DDS microservice component.
A Variable represents one selectable quantity within a Dynamic Layer (for example: temperature, precipitation, wind speed). It defines the styles, spatial aggregations and time aggregations available for that quantity.
A Dynamic Layer may have several Variables, but each variable name must be unique within that layer.
To create a new Variable:
| Field | Required | Description |
| Name | Yes | Variable identifier used by DDS. It must be unique within the selected Dynamic Layer. |
| Description | Recommended | User-facing description to identify the quantity in Dewetra3. |
| Is Default | Recommended for one variable | Makes this the default variable for the layer. Setting a new default clears the previous one, as only one default is allowed. |
| Dynamic Layer | Yes | Parent Dynamic Layer. |
| Allowed Spatial Aggregations | No | Boundary datasets that Dewetra3 may use to aggregate this variable. |
| Allowed Time Aggregation | No | Time periods and operations available for this variable. |
| Time Aggregation | No | Default time aggregation (must be selected from the allowed list). |
| Allowed Styles | No | Styles available for the unaggregated variable. |
| Default Style | No | Default style (must be selected from the allowed list). |
| Properties (JSON) | No | Variable-specific DDS parameters. The value must be a JSON object. |
An example of simple variable properties is:
{
"dt": "1",
"mu": "mm"
}
The accepted keys depend on the DDS component used by the Dynamic Layer. Always preserve the expected spelling and data type.
A Dynamic Layer View is the presentation profile exposed to Dewetra3 or other applications.
It binds together one Variable to an optional Style, one or more View Groups, and optional spatial aggregation variants.
To create a Dynamic Layer View:
To Configure spatial aggregation variants:
Use Add Spatial Aggregation to define each aggregation variant exposed by the view.
| Field | Description |
| Aggregation | Spatial Aggregation allowed by the selected Variable. |
| Style | Style used to render the aggregated result. This can differ from the main Variable style. |
| Aggregation type | Statistical operation: mean, min, or max. |
| Is Default | Sets the aggregation initially used by the client. Only one row can be the default. |
If the default row is removed, the GUI automatically assigns the first remaining row as default.
A view can also be saved without any spatial aggregation.
If a Dynamic Layer does not appear in Dewetra3, verify all the following requirements:
A Series Layer defines time‑series data displayed in Dewetra3, such as sensor observations, deterministic forecasts, or probabilistic forecasts.
Unlike Dynamic Layers, Series Layers do not require a separate Variable or Dynamic Layer Views: their View Groups are configured directly inside the Series Layer.
To create a Series Layer:
| Field | Required | Description |
| Data ID | Yes | Unique identifier for the series. Locked in Edit mode. |
| Description | Recommended | Human-readable series description. |
| Unit of Measure | Recommended | Unit displayed with values (e.g., mm, m, °C). |
| Instances | Operationally required | DDS deployments that serve the series. |
| Layer Group | Required for scoped operation | Defines portal/domain ownership and restricted‑user visibility. |
| View Group | Required for application visibility | Portal/domain/application contexts in which the series is exposed. |
| Type | Required for new records | Observation, deterministic forecast, or probabilistic forecast. |
| Properties (JSON) | Generated | Read-only properties derived from Type and Sensor Class. |
| DDS component | Generated | Read-only DDS component derived from Type. |
For Observation series, select a Sensor Class.
The GUI generates the sensor-series component and the corresponding sensors.* properties.
Registry fields are not used for Observation Series.
| Sensor Class | Stored sensor class | Typical use |
| Hydrometers | 3 | Water level or hydrometric observations. |
| Rain gauges | 2 | Precipitation observations. |
| Thermometers | 5 | Temperature observations. |
For Deterministic Forecast or Probabilistic Forecast, configure the registry fields:
| Field | Description |
| Registry Layer | Static Layer containing the geographic features associated with the series. |
| Registry ID Field | Attribute that uniquely identifies each feature and links it to series data. |
| Registry Description Field | Attribute used as the human-readable feature label. |
The available fields are read from the selected registry layer.
If the lists are empty, verify that:
The GUI generates the forecast‑series properties and DDS component automatically. At runtime, the registry Static Layer may need to be published before the series can be used.
A Static Layer references a file stored in a configured Bucket and associates it with a Style.
Static Layers can be:
Before creating a Static Layer, verify that:
.shp, .shx, .dbf, .prj);Supported formats typically include raster and vector resources, such as GeoTIFF, GeoPackage, and Shapefile packages. Actual support depends on the publication service and deployment configuration.
To create a new Static Layer:
| Field | Required | Description |
| Name | Yes | Unique identifier. Whitespace is rejected. Locked in Edit Mode. |
| Bucket | Yes | Storage definition containing the source object. |
| Path | Yes | Object path relative to the Bucket. Case-sensitive. |
| Style | Yes | Style associated with the published layer. |
| Publication | Read-only | DDS/GeoServer instance recorded after successful publication. Blank means not yet published. |
| Layer Group | Required for scoped operation | Portal/domain ownership and restricted-user visibility. |
| View Groups | Required for direct application visibility | Applications in which the Static Layer can be exposed. Not required when the layer is only used for internal aggregation or registry dependency. |
The Publish action first saves the record and then requests its published URL from the backend.
The backend selects an eligible DDS/GeoServer instance configured to publish static layers, uploads or updates the data and style, and records the publication instance.
Publication is a separate operational step from saving:
After publication, reopen the record and verify that the Publication field is populated.
Then check the layer in Dewetra3 or in the target map service, as appropriate.
The Dewetra3 station registry is synchronized with CIMH’s cloud-hosted MongoDB database. A daily job reads the weather station registry from MongoDB and updates the internal Stations and Sensors tables.
Each run performs a single synchronization and then exits. The job only reads from MongoDB, and no measurements or time series are transferred at this stage. Records that exist in the registry but are missing from the source are not deleted.
Once a new station is added to the Anagrafica, it is not immediately visible on the platform: it must first be assigned to one or more Station Groups before becoming visible to users.
The connection to MongoDB is established through an SSH tunnel to the AWS server hosting the service.
Regarding time series data, a separate job runs every 5 minutes and retrieves observations from the same cloud-hosted MongoDB database. The job currently imports all available observations for the following types:
The process imports all available measurements that are no older than 12 hours and belong to sensors already registered in the station registry.
As with the registry synchronization process, the connection to MongoDB is established through an SSH tunnel. The execution frequency can be adjusted as needed.
A Spatial Aggregation links a polygon Static Layer to the attribute that uniquely identifies each area.
Variables can allow one or more Spatial Aggregations, and Dynamic Layer Views can assign a rendering style and statistical operation to each one.
An incorrect ID Field may allow the configuration to save, but will cause missing, merged, or unidentified areas at runtime. Always verify that the field is populated and unique for every feature.
DDS Instances identify the DDS or GeoServer deployments used by layer configurations and publication workflows. They store service credentials and must be managed only by authorized administrators.
Instance fields:
| Field | Required | Description |
| Name | Yes | Unique identifier for the deployment. Locked in Edit mode. |
| URL | Yes | Base URL of the DDS or GeoServer service. |
| Username | Yes | Service account username. |
| Password | Yes | Service account password. Use the eye control only when disclosure is safe. |
| Instance Type | No | Classification: Development, Testing/Staging, or Production. |
| Allow Static Layers | No | Makes the instance eligible for static‑layer publication. Enable only for an appropriate map service. |
Do not assign a Production instance to a test configuration. Before changing the URL or credentials, coordinate with the owners of all Dynamic Layers, Series Layers, and published Static Layers that rely on that instance.
Supporting resources are usually opened through the +, eye, pencil, or copy controls next to a selector.
A Layer Group contains:
Its internal name is derived from these values.
Layer Groups define configuration ownership and the visibility scope for restricted dynamic/static configurators. Restricted users can manage only the groups that belong to their permitted portal and coordinated domains.
A View Group contains:
Use the exact application identifier expected by the target Dewetra3 deployment. If a record is assigned to a different application View Group, it will not be returned in that context, even if portal and domain match.
A Bucket contains:
| Field | Description |
|---|---|
| Name | Unique storage identifier. |
| Description | Human‑readable purpose or owner. |
| URL | Base location. Supports HTTP(S), FTP(S), and s3:// locations are supported by the data model. |
| Credentials | Credential reference or profile used to access the location. Do not place credentials in documentation or layer paths. |
| Layer Group | Groups allowed to use or manage the Bucket. |
A Style contains:
For GeoServer publication, the Path identifies an SLD file.
Match the style to the source geometry and value domain.
For Dynamic Layer Views, the main Style selector is limited to the styles allowed by the selected Variable. Styles for aggregated results are selected separately in each aggregation row.
A Time Aggregation contains:
After creating a Time Aggregation, enable it in Allowed Time Aggregations for the appropriate Variables and optionally select it as the Variable’s default Time Aggregation.
Use Clone when testing a significantly different component, source, or presentation profile.
Before deleting a resource, inspect all configurations that depend on it.
| Resource | Check before deleting |
|---|---|
| DDS Instance | Dynamic Layers, Series Layers, and Static Layer publications. |
| Bucket | Styles and Static Layers. |
| Style | Variables, Dynamic Layer Views, aggregation rows, and Static Layers. |
| Static Layer | Spatial Aggregations, Series Layer registries, View Groups, and publication state. |
| Spatial/Time Aggregation | Variable allowed/default selections and Dynamic Layer Views. |
| Dynamic Layer | Variables and their Dynamic Layer Views. |
| Variable | Dynamic Layer Views. |
| Layer/View Group | Every configuration assigned to that scope. |
| Symptom | Likely cause | Action |
|---|---|---|
| 403 Forbidden | Missing role or resource outside allowed Layer/View Groups. | Verify application roles, portal/domain, coordinated domains, and allowed groups. |
| 404 or “not found” | A selected dependency was deleted or is outside the visible scope. | Reopen the selector and choose an existing permitted resource. |
| 409 Conflict/ Duplicate error | Name, Data ID, or unique group combination already exists. | Choose a unique identifier or edit the existing record. |
| Invalid Properties/ Coverage JSON | Malformed JSON, array, or scalar instead of an object. | Validate syntax and ensure the top‑level value is an object (e.g., {}). |
| Save button disabled for a Static Layer | Name contains whitespace, the form is read‑only, or a save is already running. | Remove whitespace or open Edit mode. |
| Empty selector | No resource exists, the resource is not assigned to an allowed group, or the user lacks access. | Create the dependency or correct group assignments/roles. |
| Changes lost warning | Navigation was requested after modifying the current form. | Save, or confirm only when changes should be discarded. |
Saving confirms that configuration metadata was accepted; it does not guarantee that source data is readable or that the application context matches.
Check, in order:
Verify:
Registry field selectors are populated by inspecting the selected Static Layer.
Confirm that the layer is a readable vector dataset, its Bucket and Path are correct, and its attributes contain suitable identifier and description fields.
Dynamic Layer
□ Data ID is unique and stable.
□ Correct DDS Instance and Layer Group are selected.
□ DDS component and JSON properties match the source.
□ At least one Variable exists; a default is selected when required.
□ Allowed/default styles and aggregations are coherent.
□ At least one Dynamic Layer View exists.
□ View Groups match the target Dewetra3 context.
□ Data and rendering have been verified in Dewetra3.
Series Layer
□ Data ID, description, and unit are correct.
□ Correct DDS Instance, Layer Group, and View Groups are selected.
□ Type and Sensor Class, or forecast registry fields, are complete.
□ Generated Properties JSON and DDS Component are correct.
□ Registry Static Layer is available/published when required.
□ Series and feature labels have been verified in Dewetra3.
Static Layer
□ Name contains no whitespace.
□ Bucket, Path, and source files are correct.
□ Style exists and is compatible.
□ Layer Group and View Groups are correct.
□ Publication was completed when required.
□ Publication field and target map output were verified.
□ Direct visibility or dependent aggregation/series behavior was verified in Dewetra3
| Term | Meaning |
|---|---|
| DDS | Data service used to resolve and serve configured layers and series. |
| Dewetra3 | Client application in which configured map layers and series are displayed. |
| Data ID | Stable unique identifier of a Dynamic Layer or Series Layer. |
| Dynamic Layer | DDS‑managed dataset whose variables and presentation views are configured separately. |
| Variable | Selectable quantity belonging to a Dynamic Layer. |
| Dynamic Layer View | Application‑facing presentation of one Variable, with style, groups, and optional aggregations. |
| Series Layer | Time‑series configuration for observations or forecasts. |
| Static Layer | File‑based vector or raster layer stored in a Bucket and optionally published to a map service. |
| Registry Layer | Static vector layer whose features identify the locations or entities associated with forecast series. |
| Spatial Aggregation | Polygon layer plus identifier field used to aggregate dynamic values by area. |
| Time Aggregation | Named time period and statistical operation enabled for a Variable. |
| Layer Group | Portal/domain scope used for ownership and restricted configuration access. |
| View Group | Portal/domain/application scope used for application visibility. |
| DDS Instance | Configured DDS or GeoServer deployment, including URL and service credentials. |
| Bucket | Storage endpoint and credential reference containing layer or style files. |
| Publication | Deployment of a Static Layer and its Style to an eligible DDS/GeoServer instance. |