3.5.036

INDEX

INVENTORY

Some edition processes trigger changes on connects and its links. In this relase, connects (connec and gully) with assigned arc_id but without graphic link connection have been identified and correctly managed on every edition process with affectation on them.

The goal of this change is to avoid incorrect or missed arc_id assignations and automatize reconnection to the proper arc.

On detail, the processes which have been evaluated and repaired are:

  • Insert PLANIFIED node over OPERATIVE node.

  • Arc divide.

  • Arc fusion.

  • Feature replace PLANIFIED.

Keep selector scroll when checking a new item

Util this release, if the list of items on the selector were so large that scroll down was needed, the check of a new item returns the position to the top.

Now it has been reparied and the position on the selector is keeped when checking a new item.

New columns on minsector table

Four new columns have been added to minsector table to enhance its stats. It will be useful to summarize information of this map zone.

New fields are:

  • num_border: Number of border features separating one minsector from another.

  • num_connec: Number of connecs within the minsector.

  • num_hydro: Number of hydrometers within the minsector.

  • length: Total length of the newtwork within the minsector.

EPA

Add new source pattern from inp_connec when new scenario is created

On Giswater's Toolbox process of Create Demand Dscenario from CRM, the possibility of creating a new Scenario using the Connec - Patterns has been added. Values from v_edit_inp_connec table will be used to create this new Scenario.

EPA result manager: "Set corporate" button is now "Toggle corporate"

The EPA result manager button functionality has been changed. Now is possible to set different results as corporative, because they can be related to different exploitations. Until now only one result could be corporate.

Set corporate button toggle the value of iscorporate on rpt_cat_result table. On corporate tables (node_add, arc_add, connec_add), result values are inserted or deleted. If feature id's collide, the inserted one will update old one.

MASTER

Refactor strategy of execute psector. New traceability tables for executed and canceled psectors

Psector execute modes have been changed with the goal of making the manage of executed features easier, without having trouble between operative and planified topologies.

In order to achieve this, now, when executing or canceling psectors, its related features will be moved to traceability tables where consulting data will be clear and easy. Psector manager will still keep the alphanumerical basic data and the poligonal geometry around the existing features, but there will be no relations with inventory features.

New traceability tables are:

  • audit_psector_arc_traceability

  • audit_psector_node_traceability

  • audit_psector_connec_traceability

  • audit_psector_gully_traceability

These tables will contain all the information stored on plan_psector_x_* tables plus the executed action (EXECUTE or CANCEL) plus all the information on inventroy table (arc, node, connec, gully).

As a result of the refactor there are 5 different psector states, with its related actions:

  • PLANNED - No action

  • ON GOING - No action

  • EXECUTED (Save Trace) - Related features will be inserted to traceability tables with Execute psector action.

  • EXECUTED (Set OPERATIVE and Save Trace) - The elements that were planified will become OPERATIVE state. The elements that were planned to be removed from the psector will become OBSOLETE state. In order to also mantain traceability, related features will be inserted to traceability tables with Execute psector action.

  • CANCELED (Save Trace) - Realted features will be inserted to traceability tables with Cancel psector action.

Traceability tables are ready to load onto QGIS project using Giswater's Load Layers button. By default, a useful symbology will be setted to establish a visual difference between planified features, obsolete features and affected features. Of course this simbology can be modified by user to set a more accurate style according to the needs.

Last updated