We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

What is new in Giswater 3.5

00:00

Formal Metadata

Title
What is new in Giswater 3.5
Title of Series
Number of Parts
351
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2022

Content Metadata

Subject Area
Genre
Abstract
Giswater (giswater.org) is a open source software aimed at being a corporate tool in water utilities with which to manage network assets in an excellent way and at the same time have the assets ready for hydraulic simulation, a feature that today Today it is known how to have a digital clone of network assets. Technologically, it uses a set of Open Source technologies such as EPANET, SWMM, PostgreSQL, PostGIS or QGIS, all of them mature and proven, which give it a very powerful base for growth and consolidation. Its 'database centric' architecture gives it enormous potential with which maintenance operations (network outages) can be managed in an integrated way, longitudinal profiles can be made, events inventoried, among others. It has a data model with dual-face architecture, which allows full integration of inventory and hydraulic model data, both for drinking water networks and for urban drainage and sanitation networks, giving full flexibility to the modeler to work with hydraulic capacities without any impact on inventory data for each asset item. The EPA file export module has certain "on the fly" transformations to make the two different geometries (remember the dual-face) of the inventory elements compatible for both EPANET (GitHub: /Giswater/giswater_dbmodel/ wiki/epanet-on-the-fly-transformations) how to for SWMM. It allows you to work with different scenarios to create different modeling conditions in order to check the worst case scenario or check how the network will respond in future scenarios. For Water Supply networks it is possible to work with demand scenarios (GitHub: Giswater/giswater_dbmodel/wiki/epa-demand-scenarios) and for Urban Drainage projects it is possible to work with DWF scenarios (GitHub: Giswater/giswater_dbmodel/wiki/epa-dwf-scenarios) and hydrological scenarios (GitHub: Giswater/giswater_dbmodel/wiki/epa-hydrology-scenarios) Additionally, it also allows working with alternatives to plan new elements of the network without interfering with the elements of the asset inventory. By creating an alternative (GitHub: Giswater/giswater_dbmodel/wiki/masterplan-capabilities) you can modify the physical reality of the network without affecting the real assets at all. Another especially interesting feature is that it allows collaborative work. Large hydraulic engineering projects have been worked on to date in a sequential or fractional way, but not collaboratively. Thanks to Giswater it is now possible to work on projects in a real collaborative way, given the inherent multi-user characteristics of the Databases on which the project pivots. The project was born seven years ago and in its version 3.5 it incorporates interesting novelties, among which the following stand out: Complete refactor of the python code, new hydraulic model capabilities with the management of multi-scenarios or the improvement of the usability of numerous tools such as dynamic zoning or the info among others.
Keywords
Open setFreewareProcess (computing)Machine visionUsabilityEnterprise architectureSimulationSoftwarePhysical systemInformation technology consultingData managementIntegrated development environmentMobile WebWeb 2.0BitTemplate (C++)SoftwareEndliche ModelltheorieData modelOrder (biology)Water vaporProjective planeMachine visionCustomer relationship managementWeb browserWeb serviceWeightMultiplication signComputer animation
Code refactoringOpen sourceInsertion lossStatisticsCodeData modelSource codeCone penetration testLine (geometry)Plug-in (computing)DatabaseExact sequenceScripting languageTrigonometric functionsInformationComputer networkDedekind cutMaxima and minimaGUI widgetElement (mathematics)MathematicsForm (programming)Bit rateDiameterNominal numberAbelian categoryEvent horizonPrincipal idealComputer-aided designCalculusVisualization (computer graphics)Electric currentData managementState of matterRadio-frequency identificationPeer-to-peerElectronic visual displayCurveAsynchronous Transfer ModeDifferent (Kate Ryan album)Coma BerenicesComputer fileType theoryMiniDiscMathematical analysisEstimationComputer configurationProcess (computing)Default (computer science)System administratorTopologyError messageControl flowRule of inferenceCheat <Computerspiel>Vertex (graph theory)Decision support systemPressureCodierung <Programmierung>Addressing modeNumbering schemeRotationDiscrete element methodAerodynamicsCalculationTime zoneOpen setElement (mathematics)Projective planeForm (programming)LengthInformationVolume (thermodynamics)Graph coloringTouchscreenWater vaporOrder (biology)Characteristic polynomialAlgorithmBus (computing)ResultantSoftwareData modelProcess (computing)Utility softwareBitGUI widgetData managementConfiguration spaceElectronic mailing listMathematicsSystem administratorLevel (video gaming)Connected spaceDifferent (Kate Ryan album)Endliche ModelltheorieComputer fileService (economics)Interactive televisionFunctional (mathematics)Operator (mathematics)NumberRight angleSoftware developerVelocityPressureGoodness of fitWebsiteTerm (mathematics)DatabaseCASE <Informatik>Pattern languageProjektive GeometrieTraffic reportingTheory of relativityPairwise comparisonRepository (publishing)Film editingSampling (statistics)StatisticsPoint (geometry)EmailComputer-assisted translationAdditionDefault (computer science)DigitizingSolid geometryCapability Maturity ModelMereologyWikiData warehouseBenutzerhandbuchPresentation of a groupAsynchronous Transfer ModeMultiplication signState of matterMathematical analysisEstimatorCode refactoringPlanningLogicExterior algebraRepresentation (politics)Revision controlNetwork topologyCodeMaxima and minimaPlug-in (computing)Error messageGame controllerTwin primeComputer animationXMLEngineering drawingDiagram
Transcript: English(auto-generated)
Thank you. First of all, let me say thank you so much for being here at 9 o'clock after yesterday's party. I actually appreciate your effort to be here. Thank you so much. Okay, as Gaben said, we will talk a little bit about what is new in GIS Water 3.5.
Let me present before me and my company and my colleague. We come from BGO. BGO is a consultancy firm for more than 15 years old. We are based in Barcelona and our region is water and sanitation for all.
I am the partner director of BGO and the technical manager of the GIS Water Association, as well as Albert is project manager at GIS analyst in BGO and member of the technical committee of the GIS Water Association.
What is GIS Water? It's a software based on QGIS and PostgresQL, which has a huge plug-in and a huge template on Postgres,
in order to connect both with APACnet and a stormwater management model to make hydraulic modeling for water supply systems, seawash systems and urban drainage. At the same time, it enables to make a good environment to asset management
and as well as is based on PostgresQL and QGIS, it's very easy to connect with other systems like mobile devices, web browsers,
customer relationship managers, softwares, SCADA, etc. You can use web service, you can use ODBC, what you want. We are right now here at 2022, talking about 3.5% of GIS Water.
In fact, project start at 2014 in Barcelona. During these eight years, several releases have been developed
and right now we are on 3.5, which I will present to you a little bit. But before this, why GIS Water? GIS Water is the first step to manage a water supply company,
water utility, to put water utility on the 21st century. Because when you have a good inventory, when you can start to work with asset management, when you have topology, when you have good quality data, you are able, after this, to create a water data warehouse
and to start to work with digital twins and advanced operation. This is the first step. And what are the main changes here in new 3.5 version?
First of all, it has been finished a huge refactor, including the model and Python plugin. Everything has been refactorized in order to make it easier for developers. The documentation has been increased and day by day
we try to document better on GitHub. Furthermore, there is a continuous improvement of existing functionalities. We are very pleasure to listen users
and to adapt and to incorporate the tiles, little things that make easy their work. And also, new functionalities have been created oriented to big projects.
Right now, JSWater has been used in a very big project in Latin America, in fact, one whole country. And more than 20 engineers, they draw and digitize water networks. In order to make this possible,
a few functionalities have been created oriented to this kind of big projects, making a good traceability of what user is doing, making a good traceability in terms of health check,
in order to detect the quality of database, as well as some functionalities have been created in order to make it easier. Also, how people need to draw, how people can split pipes, how people can fusion pipes.
Little things, the main buttons, the main workflows, was being developed before. Little things that make it easier to work with. Albert will be focused more in what is doing 3.5 and what JSWater does.
Anyway, as we know, because we don't have control about who uses, as we know, more than 30 utilities, which they manage more than 400 municipalities in five countries,
and more or less 8 million people, served people, is the numbers in terms of users, the numbers in terms of code. Here you can see both the main repositories, the GISWaterDV model on GitHub,
and the GISWaterQJS plugin also on GitHub. And that both repositories right now, Here there are some kind of statistics, and you can see, I think, numbers talk by themselves,
in terms of efforts, in terms of maturity of code, etc. And you can find us, you can find the project, the plugin, the user's manual, and the wiki on the GISWater.org and the GitHub slash JSWater.
And that's all for my part. Right now, my colleague Albert will continue explaining a little bit the main characteristics, the main things of JSWater.
Thank you. Okay, in this second part of the presentation, I will explain some of the main tools and best capabilities that GISWater have right now.
The plugin have 38 buttons or tools, divided in six different toolbars, which will be available or disabled, depending on the role of the user in the database. As Tobias said, we manage these different roles,
having a basic user will have basic tools, a more advanced user will have more advanced tools, and, for example, an admin user will have the whole plugin enabled. We have prepared the logical or the list of characteristics
which are representative of what GISWater is, as you can see on the screen. They are custom info, edit tools, Mincat, hydraulic models with Epanet, Planify Network, and Toolbox. So, let's start with the first one I want to show you today,
which is InfoTool. This one is one of the most distinctive tools that GISWater have. We have developed our own custom info, so using this, user can click on any element of the network,
having pipes, nodes, and connects, no matter the active layer they have, and a custom form will be opened in a single click. This way, users can easily consult information about its network.
Another great characteristic related to this tool is the customization of the network data forms. Here, database administrators can choose which information will be shown in the forms. So, what can be done on the custom forms?
We can change levels and their size and color, you can hide unnecessary widgets, you can also rearrange widgets, you can assign mandatory data, and among other advanced configurations,
like depending values, refreshing depending on other values. Also, we can configure combo lists, etc. Here, looking at the pictures, it's an example. We have the same information for one hydrant,
the number 1009, but in the left picture, the left one, we have the default configuration, and in the right one, the forms have been configured, changing level colors, changing widget order, and, of course, hiding unused widgets.
So, it's really easy in comparison to consult and to read the information of these forms. And all of this, using SQL in the database,
so you can change the database and this form will be changed automatically. Second one, addition tools. In this case, I'm talking about toolbar, not just one tool. These buttons are needed to edit and maintain inventory
using them and, of course, another QGIS default buttons. Users can digitize new network, downgrade obsolete elements, replace or change features, etc. There are also two specific buttons
developed as CAD tools, which will allow users to accurately digitize. Of course, other QGIS tools, like, for example, advanced digitizing panel, can also be very helpful to accurately digitize. As a database-centric project,
of course, all the changes will be automatically saved in the database, so instantly available for other users. In this related picture, we see a network with a simple example of a network, our sample data, with digitizing support points,
which then we can use to add the network with the addition tools of gs-water. Another great characteristic is MinCAT. MinCAT is the minimum cut of the network to live without water at one specific point. Here we have two different tools.
The first one creates a new MinCAT, and the second one, here you can see, the second one manages current and historical MinCATS. When clicking and when using the first button,
if we click the point we want to close, an algorithm will calculate the affected network and the bulbs which must be closed to execute this MinCAT. As a result, we will have the data about pipes, length, water volume, connects, connections, and customers affected by this MinCAT.
And then using the second tool, the MinCAT Manager, it is possible to do such things as manage MinCAT states, which are planified, in progress, or execute. We can also planify unexpected start dates,
and also we can recalculate, of course, the affectation of the network of this MinCAT at any time. But this would be also important only if the network has suffered changes since the MinCAT planification. Here in the example we can see
a result of the MinCAT process, both in the canvas having different layers as a result, which we can see proposed bulbs to close in red color, and also bulbs which will not operate even if we close them in green,
and of course the affected pipes in this color, in this layer. And also we have the data in the form, in canvas,
with the data of this affected network, the length, etc. The fourth characteristic I want to show you today is its interaction with EPANET, which is another major characteristic of GIS Water.
The interaction with EPANET and hydraulic models. Here we have a specific toolbar with five buttons to manage the hydraulic toolbar. It's possible to export and import .TMP files, and of course run the hydraulic model
to finally display the results on QGIS. Here users will have the ability to manage different demand scenarios, different patterns, and different curves, among other custom configurations like network export modes, etc.
It's also possible to compare different models using the result selector tool, and here in the example we have our sample data with the result of the hydraulic model, which will display the velocities, pressures,
and other data of the pipes on QGIS, using QGIS layers. And of course, as always, a log file to have the data. Planified network is another great characteristic.
GIS Water, it's important to know here that we use three different states for network elements on service, obsolete, and planified. This final one, planified, allows users to project new alternatives to the current network. The great characteristic here is that these alternatives,
these projects won't affect on service network, but they will maintain the topology allowing analysis for each one of these projects using it on EPANET or using it on MinCAT, of course, for example.
It's also important to notice that pricing can be added to get the project estimate budget, which will be automatically generated if pipes have their own price. In the example, we have both pictures of on service network
and in the right side with a planified project. And finally, as the last one, GIS Water Toolbox is another great characteristic we have recently. It's more or less like QGIS Toolbox. Here, users can run different processes, which are grouped by roles of GIS Water.
Some of them can be used to fix topology errors, which can be detected with the toolbox itself, or as Javier mentioned, the check project tool, which will return a full report of the health of our database,
just clicking this tool. Here we have, in the first related picture, this check project which I was saying about, with critical errors, there are no warnings and other info that has been checked and there is no problem with them. And also here, the toolbox that I was talking about.
And that's all. GIS Water has many other tools. I think we don't have more time today to explain them, but you can visit our project website. Okay, thank you.
You can visit the project website where lots of more information is available, if you are interested. And that's all. If you want to contact with us, you have our mails here. Thank you.