> 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.5.027.md).

# 3.5.027

## INDEX

* [#inventory](#inventory "mention")
  * [#display-messages-in-forms-instead-of-the-canvas](#display-messages-in-forms-instead-of-the-canvas "mention")
  * [#add-node-rotation-logics-on-ud-projects](#add-node-rotation-logics-on-ud-projects "mention")
  * [#new-variable-to-customize-link-field-using-google-maps-geolocalization](#new-variable-to-customize-link-field-using-google-maps-geolocalization "mention")
  * [#enhance-delete-feature-allow-delete-nodes-connected-to-obsolete-arcs-bug-fix-and-show-on\_service-obs](#enhance-delete-feature-allow-delete-nodes-connected-to-obsolete-arcs-bug-fix-and-show-on_service-obs "mention")
* [#om](#om "mention")
  * [#allow-recalculate-a-mincut-from-another-point-when-is-planified](#allow-recalculate-a-mincut-from-another-point-when-is-planified "mention")
  * [#new-toolbox-function-to-find-reach-of-hydrants](#new-toolbox-function-to-find-reach-of-hydrants "mention")
* [#epa](#epa "mention")
  * [#show-message-if-curve-is-invalid](#show-message-if-curve-is-invalid "mention")
  * [#add-the\_geom-on-waterbalance-views](#add-the_geom-on-waterbalance-views "mention")
* [#system](#system "mention")
  * [#add-widget-to-hide-querytext-in-toolbox-reports](#add-widget-to-hide-querytext-in-toolbox-reports "mention")
  * [#new-db-variable-to-manage-snapping-configuration](#new-db-variable-to-manage-snapping-configuration "mention")

## INVENTORY

### <mark style="color:blue;">Display messages in forms instead of the canvas</mark>

When an **error or info message** returns from an action in the form of the elements, this message will be **shown in the top of the form**. Here is much more **easy to read** compared to the top of the canvas, where it can be hidden or unnoticed.

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

### <mark style="color:blue;">Add node rotation logics on UD projects</mark>

Automatic node rotation logics was only available in WS projects until this version. Now the same logics have been added to UD projects, so **automatic rotation for nodes will be calculated** if Config tool '*Disable node rotation on update'* isn't checked. If checked, this calculation will be disabled.

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

### <mark style="color:blue;">New variable to customize link field using Google Maps geolocalization</mark>

A new variable have been added to enable **automatic fill of link data** for point elements (node and connec) using **Google Maps geolocation**.

To enable it you just need to set ***{"google\_maps":true,"fid":false}*** to ***edit\_custom\_link*** variable on ***config\_param\_system*** table.

With this variable enabled, each time a new node or connec is added, link field will be automatically filled with Google Maps URL to the exact position of the element.

This link can be easily opened by clicking on the path or using the **Open link** button on the top of the form.

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

### <mark style="color:blue;">Enhance delete feature: allow delete nodes connected to obsolete arcs (bug fix) and show on\_service/obsolete arcs on getfeaturerelation</mark>

*Delete feature* tool have been improved by fixing a bug which doesn't allow users to delete nodes that have relations with obsolete arcs.

Besides, now the tool shows if arcs are *on service* or *obsolete* before on *Show feature relations*.

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

## OM

### <mark style="color:blue;">Allow recalculate a mincut from another point when is planified</mark>

Now it's possible to **fully recalculate a mincut**, even **changing it's initial point**. Until now it was only possible to recalculate having the same initial point.

To do so it's as simple as open mincut form and use again *Automatic Mincut* tool to recalculate clicking on another point. Affected network will be updated, but the data already filled will be mantained unless it is changed by user.

### <mark style="color:blue;">New toolbox function to find reach of hydrants</mark>

A new function have been added to Giswater's Toolbox. Not only will allow users to **calculate the reach to the current hydrant network**, but also will help **defining new hydrant location**.

There are different steps to take into account:

* **Firehose range** - Variable length of the fire hose which will be used to calcul. By default 100 meters.
* **Process mode**
  * **Influence area** - Calculates influence area of the current hydrant network.
  * **Hydrant proposal** - Duplicates firehose range to allow defining location of new hydrants.
* **Use proposed hydrants** - If checked, calculation will sum current hydrant network with new proposed hydrants defined in v\_edit\_anl\_hydrant layer. To add new hydrants to this layer is as simple as load it into the project and insert new points on desired places (no data needed).
* Use selected psector - Takes into account currently selected psectors. If they have hydrants, it's influence area will be calculated.

The **result** of the process will be shown in **temporal layers** automatically loaded into ToC.

{% hint style="warning" %}
Notice that this process could be only used if ***om\_streetaxis*** table on the DB is **filled**.&#x20;

The goal of this table is to have the **streetaxis information**, same as *ext\_streetaxis* table, but **divided** in every street crossing.
{% endhint %}

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

<figure><img src="/files/8k4x4sFWenXOBU24dZ8W" alt=""><figcaption><p>Result of the process using Influence area mode with current hydrant network.</p></figcaption></figure>

## EPA

### <mark style="color:blue;">Show message if curve is invalid</mark>

When adding a new curve using Non-Visual object manager and values are invalid, a warning message will be shown to users.

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

### <mark style="color:blue;">Add the\_geom on Waterbalance views</mark>

Geometry field have been added to waterbalance related views, so they can be loaded into QGIS projects and visualize waterbalance data using it's dma geometry. Affected views are:

* v\_om\_waterbalance
* v\_om\_waterbalance\_loss
* v\_om\_waterbalance\_nrw

## SYSTEM

### <mark style="color:blue;">Add widget to hide querytext in Toolbox reports</mark>

Query used in Toolbox's reports now can be hide or shown using a simple widget.

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

### <mark style="color:blue;">New variable to manage snapping configuration</mark>

A new variable named ***utils\_use\_gw\_snapping*** have been added to *config\_param\_system* table. If its value is TRUE, Giswater's tools will automatically configure snapping options for network layers each time they are used. Otherwise, if FALSE, Giswater's tools will never change any snapping options, allowing a complete customized configuration in QGIS projects.