Abstract
The main purpose of this article is to show how to extend an existing open source database, namely QWAT (Acronym from Quantum GIS Water Plugin), by using pgRouting (PostgreSQL routing extension) in order to achieve the ability to find the water flow in a water network. The water path in a water network is a key information needed by any water supplying company for different activities such as customer identification, meter the water flow or isolating areas of the water network. In our environment an open source database was used and that database didn’t have any means to identify the water path, so our research is intended into that direction. Once a water path is found, our next goal was to show that identifying customers for a water supplying company is just a click away (by using no directional graphs). Another key information needed by the water supplying companies is to know which valves should be closed in order to shut off the water for an area of the water network. As result, the second purpose of the article is to show how to identify the necessary valves, to be closed or open, in order to shut off or on the water (within the pipe network).
Highlights
Water supplying companies all over the world needs to know who their customers are and this task is a very important one, for reasons like: knowing to whom they will invoice, knowing how much water was used and if a leak occurs to identify which valves needs to be closed in order to shut off the water
In the abstract of this paper, we said that we want to show a way of finding the water path within QWAT databases, but if the pipe table does have a first and a second node, why QWAT model doesn’t have a water path function until the final consumer? Or does it? The answer is given by QWAT designers, into their documentation, where they presented how the QWAT model should be used
We showed in our article how an existing open source water network model (QWAT model) can be changed in order to accommodate new requirements, but it was only one of the steps we’ve done to improve the QWAT model
Summary
Water supplying companies all over the world needs to know who their customers are and this task is a very important one, for reasons like: knowing to whom they will invoice, knowing how much water was used and if a leak occurs to identify which valves needs to be closed in order to shut off the water. In the abstract of this paper, we said that we want to show a way of finding the water path within QWAT databases, but if the pipe table does have a first and a second node, why QWAT model doesn’t have a water path function until the final consumer? If a QWAT database is filled the way described above, the water path should be available, but not to the final user/consumer, because, usually, water supplying companies have their own software for customer management and invoicing. The current paper will continue with the following chapters: Database Background, Database Proposed Changes, Applied Research, Results and Conclusions
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
