> For the complete documentation index, see [llms.txt](https://giswater.gitbook.io/change-log/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://giswater.gitbook.io/change-log/3.6.016.md).

# 3.6.016

* [#inventory](#inventory "mention")
  * [#enhance-performance-for-v\_edit\_node](#enhance-performance-for-v_edit_node "mention")
  * [#enable-see-expl\_id2-objects-when-only-expl\_id-is-selected-by-managing-sector\_id](#enable-see-expl_id2-objects-when-only-expl_id-is-selected-by-managing-sector_id "mention")
  * [#change-columns-brand-and-model-for-brand\_id-and-model\_id-on-cat\_arc-cat\_node-and-cat\_grate-ud](#change-columns-brand-and-model-for-brand_id-and-model_id-on-cat_arc-cat_node-and-cat_grate-ud "mention")
  * [#add-columns-brand\_id-model\_id-and-serial\_number-for-node-and-arc-ud](#add-columns-brand_id-model_id-and-serial_number-for-node-and-arc-ud "mention")
  * [#delete-column-serial\_number-on-man\_element-ud](#delete-column-serial_number-on-man_element-ud "mention")
  * [#change-name-on-config\_param\_system-variable-from-edit\_link\_check\_arcdnom-to-edit\_link\_link2network](#change-name-on-config_param_system-variable-from-edit_link_check_arcdnom-to-edit_link_link2network "mention")
  * [#enable-the-automatic-calculation-of-label-coordinates-label-rotation-and-label-quadrant-according-to](#enable-the-automatic-calculation-of-label-coordinates-label-rotation-and-label-quadrant-according-to "mention")
* [#epa](#epa "mention")
  * [#update-timser\_id-combo-of-raingage-showing-only-active-timeseries-with-rainfall-type](#update-timser_id-combo-of-raingage-showing-only-active-timeseries-with-rainfall-type "mention")

## INVENTORY

### <mark style="color:blue;">Enhance performance for v\_edit\_node</mark>

The definition of view "v\_edit\_node" has been changed significantly with the aim of gaining performance. Now, it uses subquerys as well as retriving the information from parent table.&#x20;

### <mark style="color:blue;">Enable see expl\_id2 objects when only expl\_id is selected by managing sector\_id</mark>

Now, it is possible to see the objects from expl\_id2 by using the distinct sectors from the selected exploitation.&#x20;

### <mark style="color:blue;">Change columns</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`brand`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">and</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`model`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">for</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`brand_id`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">and</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`model_id`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">on cat\_arc, cat\_node and cat\_grate UD</mark>

Columns "brand" and "model" have been renamed to "brand\_id" and "model\_id" respectively.

### <mark style="color:blue;">Add columns</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`brand_id`</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`model_id`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">and</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`serial_number`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">for node and arc UD</mark>

New columns have been added to tables "node" and "arc" with the aim of disconnecting these attributes from the catalogs "cat\_brand" and "cat\_brand\_model" and assigning them to the objects individually. These columns also exist in view "v\_edit\_node" and work with the trigger. If these values are null, the value for that object is taken from the catalog "cat\_node" or "cat\_arc". However, the input value is not subjected to a foreign key and it is possible to set a custom value.&#x20;

### <mark style="color:blue;">Delete column</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`serial_number`</mark> <mark style="color:blue;"></mark><mark style="color:blue;">on man\_element UD</mark>

The column "serial\_number" has been removed from table "man\_element" in UD projects.

### <mark style="color:blue;">Change name on config\_param\_system variable from edit\_link\_check\_arcdnom to edit\_link\_link2network. Add maxDistance as a value and use it on linktonetwork</mark>

The parameter "edit\_link\_check\_arcdnom" from table "config\_param\_system" has changed its name by "edit\_link\_link2network". Moreover, a new key has been added to this parameter with the name of "maxDistance". This parameter is aimed to set a maximum distance at which the connec is going to be connected to the closest arc using the button "Link to network". If the distance from the connec to the closest pipe is greater than the configured "maxDistance", the connec is not going to be connected.

<figure><img src="/files/IZ5eFgR84XdTLyR0owPn" alt=""><figcaption></figcaption></figure>

### <mark style="color:blue;">Enable the automatic calculation of label coordinates, label rotation and label quadrant according to a user defined distance from the geometry and the rotation of the feature when inserting or updating a node</mark>

Now, it is possible to configure a default position for the labels of a specific feature type. The configuration for this must be done in 2 places: database and QGIS project.&#x20;

Regarding the database configuration, the key "labelPosition" can be added to column "addparam" from table "cat\_feature" to specify the placement of the label for the correspondig object. Here is an example:

```
{"labelPosition":{"dist":[1,2]}}
```

The key "labelPosition" has an array of 2 numeric values which indicate the meters in "x" and "y" axis respectively where the label has to be placed regarding the position of the inserted node. If the user has more parameters in column "addparam" from table "cat\_feature", the "labelPosition" parameter can be placed next to the existing ones separated by commas.&#x20;

As for the QGIS Project, the configuration has to be done in the Properties/Labels of layer "Node" (v\_edit\_node) as it is shown in the picture below:

<figure><img src="/files/TgpJcogUcFsIZkmv0tAm" alt=""><figcaption></figcaption></figure>

Finally, when inserting a node whose label position has been configured, the label parameters (coordinates, rotation, etc.) will be calculated and the label will eventually be placed:

<figure><img src="/files/rXsaio9EffNrR8LvsDZh" alt=""><figcaption></figcaption></figure>

At this point, several things can be done regarding the label position. The label rotation can be modified either manually in the Info Form or by changing the position of the connected pipes. Moreover, the label quadrant can be changed via Info Form and the label will be placed in the selected quadrant using the distances configured in the parameter "labelPosition" that has been mentioned before. The available values for label quadrant are the following:

* TR (top right)
* TL (top left)
* BR (bottom right)
* BL (bottom left)

<figure><img src="/files/MePOs1fOqrOsXQNPqcRi" alt=""><figcaption></figcaption></figure>

## EPA

### <mark style="color:blue;">Update timser\_id combo of raingage showing only active timeseries with Rainfall type</mark>

In the Attribute Table of view "v\_edit\_raingage", only active timeseries are available to be selected as the rainfall type for a raingage (column "rg\_id").&#x20;