Determine use of pipes in a geometric network

I am trying to understand how to use the Geometric Networks in ArcGis 10.1

For the purpose of my experiment, I built a simple network composed of a few connected pipes, one source (left triangle) and one sink (right square)

Following Esri's help documents, I managed to create the geometric network dataset and set my source and sink features as such.

My final objective is to find the segment that is the most likely to experience overcharge. Intuitively, it appears that it should be the one linking the two "blocks" with the directional arrow.

Is there a way to measure the charge over each edge of the network if, for example, I want 100 liters of water to flow from my source toward my sink? (given that all the pipes are identical in capacity)

By the way, I am also wondering why the "Set flow direction" command was able to give the direction of only one pipe, given the position of the source and the sink.

EDIT for clarity:

If I take another simplified network as example, I would like to quantify the charge/pressure on eache edge. In this network, I inject 100 units in the network from the left, and it moves to the right. While the edges in the loops only support 50, the segment in the middle has to resist to 100 units. Can ArcGis model the load of edges in a network?

• Just a quick thought but is the one arrow head on the one route between source and sink rather than just on one of the many lines?
– PolyGeo
Commented Jul 19, 2013 at 11:07
• I am sorry, but I don't quite understand your question :-/ The arrow on the segment in the middle was automatically added by the "Set flow direction" tool once I defined the source and the sink features. Unfortunately, no direction was computed for any other edge Commented Jul 19, 2013 at 12:26
• It's a while since I've looked at Geometric Networks but that arrow looks like it is at the midpoint of the shortest path route between source and sink.
– PolyGeo
Commented Jul 19, 2013 at 12:34
• Yes, if I flag my two extremities and calculate the shortest path, it uses this edge. However, it is logical since this is the only way to connect the two "groups". Is there any way to simulate the flow of water along this network by specifying a source and a sink? Commented Jul 19, 2013 at 13:43
• Damien, like @PolyGeo said, he only covered the flow direction question. What you are asking regarding pressure and flow in the pipes is a pretty complex hydraulic modeling exercise, and there are specialized packages that are designed for this exercise. Take a look at this answer to a different question, where I provide some links to software you may be interested in: gis.stackexchange.com/a/26220/1849 Commented Oct 9, 2013 at 9:26

When working with Geometric networks I find it is best to specify either a source or a sink not both.

Here is Esri help section on this topic In utility network applications, knowing the direction of flow along network edges can be essential. The commodity that flows through the network—water, electricity, and oil—has no will of its own. The network imposes flow direction by its configuration of sources, sinks, and edge direction. This is why when we talk about the flow of commodities through a utility network, we talk about it as directed flow.

The flow direction in a network can be determined using two methods:

``````Digitized direction of network edges
Through the definition of junctions that sources or sinks flow
``````

Sources and sinks drive flow through a utility network. Sources are junction features that push flow away from themselves through the edges of the network. For example, in a water distribution network, pump stations can be modeled as sources since they drive the water through the pipes away from the pump stations. Sinks are junction features that pull flow toward themselves from the edges in the network. For example, in a river network, the mouth of the river can be modeled as a sink since gravity drives all water toward it. Flow moves away from sources or toward sinks. Because flow direction can be established with either sources or sinks, it usually suffices to specify only sources or only sinks in a network (otherwise, your network may have edges with indeterminate flow).

It is important to remember that disabled features are accounted for when setting flow direction. Disabling a feature makes it act as if flow cannot pass through it. Thus, disabling a feature means that the flow direction cannot be set for the disabled features or for those features that are connected to the sources or sinks exclusively through the disabled feature. Flow direction using digitized direction of edges

Flow direction using digitized direction is determined by the following:

``````The connectivity of the network
Direction of the edge features
``````

In many networks, the digitized direction of the network edges reflect the direction flow should take through those edges. This scenario is widespread in water networks; whether they are water/wastewater networks or stream networks. If your data is set up in this manner, you can take advantage of the digitized direction to establish flow direction. Flow direction can be specified as either being with the digitized direction or against the digitized direction; however, this can only be specified at the network level, not for individual edges. Flow direction using the digitized direction of edges can only be set using the Set Flow Direction geoprocessing tool. Flow direction using sources and sinks

Flow direction using sources and sinks is determined by the following:

``````The connectivity of the network

The locations of sources and sinks in the network

The enabled or disabled state of features
``````

The decision to use sources and sinks to drive flow through a geometric network must be made at the time of network creation and is a setting applied to junction feature classes. When a network is created with junction feature classes using sources or sinks, individual junction features can then be defined as either sources or sinks. Sources are junction features that push flow away from themselves through the edges of the network. For example, in a water distribution network, pump stations can be modeled as sources since they drive the water through the pipes away from the pump stations. Sinks are junction features that pull flow toward themselves from the edges in the network. For example, in a sewer network, a wastewater treatment plant may be modeled as a sink since gravity drives all water toward it. Flow moves away from sources or toward sinks. Because flow direction can be established with either sources or sinks, you should only use sources or sinks in a network (otherwise, your network may have edges with indeterminate flow).

It is important to remember that disabled features are accounted for when setting flow direction. Disabling a feature makes it act as if flow cannot pass through it. Thus, disabling a feature means that the flow direction cannot be set for the disabled features or for those features that are connected to the sources or sinks exclusively through the disabled feature. Three categories of flow direction

After you set the flow direction for your network, an edge has one of three categories of flow direction: Determinate flow direction

If the flow direction of an edge can be uniquely determined from the connectivity of the network, the locations of sources and sinks, and the enabled or disabled states of features, the feature is said to have determinate flow. Flow direction based on digitized direction will have flow specified as either with or against the direction in which the feature was digitized based on how you defined the flow direction. Indeterminate flow direction

Indeterminate flow in a network occurs when the flow direction cannot be uniquely determined from the topology of the network, the locations of sources and sinks, or the enabled or disabled states of the features. When defining flow direction based on digitized direction, you should never have any edges with indeterminate flow.

In a network where flow direction is established based on sources and sinks, indeterminate flow commonly occurs for edges that form part of a loop, or closed circuit. It can also occur for an edge whose flow is determined by multiple sources and sinks, where one source or sink is driving the flow in one direction through the edge, but another source or sink is driving it in the opposite direction.

For example, consider a geometric network with the sources and sinks positioned like this: Indeterminate flow This example illustrates indeterminate flow.

In this case, the flow direction for edges 1 and 2 is set; however, edge 3 has indeterminate flow. To understand why edge 3 has indeterminate flow, consider the case where only the source is present. The flow along the three edges when only specifying a source This example illustrates the flow along the three edges when only specifying a source.

This results in a flow direction of edge 3 to the right.

Now, consider the case where only the sink is present. The flow along the three edges when only specifying a sink This example illustrates the flow along the three edges when only specifying a sink.

This results in a flow direction of edge 3 to the left. Due to the opposite potential flow directions of edge 3, this results in a conflict.

For each edge, if the flow direction is in agreement between both the source-only and sink-only cases, the flow direction is set to that direction (as seen with edges 1 and 2). However, if there is a conflict, as there is with edge 3, the flow direction is set to indeterminate since there are two possible outcomes.

Another example resulting in indeterminate flow would be if an edge has a source at both of its ends. Uninitialized flow direction

Uninitialized flow direction in a network occurs in edges that are isolated from the sources and sinks in the network. This can happen if the edge is not topologically connected through the network to the sources and sinks or if the edge is only connected to sources and sinks through disabled features. As with indeterminate flow, when establishing flow direction based on digitized direction, there should be no edges with uninitialized flow. Specifying flow direction based on sources and sinks

In order to establish flow direction on a geometric network using sources and sinks, you must choose the junctions in your network to act as sources and sinks that produce the correct flow direction.

After setting flow direction for your network, indeterminate flow may occur even when you know the direction of flow because the flow direction is determined by properties of the network or the features making up the network, in addition to the connectivity or locations of sources and sinks.

For example, in a water network, the flow direction in a pipe is determined by the difference in water pressure between the ends of the pipe. The pressure at each end of the pipe is affected by such things as the material out of which the pipe is made, the pipe diameter, the flow rate through the pipe, the physical configuration of the pipe (including any bottlenecks, valves, or sharp bends), the temperature of the water, the elevation of the ends of the pipe, and the connectivity of the network. Since ArcGIS deals with general networks (and not with domain-specific types of networks), this information is not used to set the flow direction. Thus, the flow direction can be set to indeterminate for some edges in these networks.

A set of similar variables exists in every domain. Developers can write custom flow-direction solvers that use these variables to find determinate flow direction in domain-specific networks.

• +1 - but please be sure to always clearly indicate any text that you have copied direct from ArcGIS Help and provide a link to that source.
– PolyGeo
Commented Jul 20, 2013 at 0:26
• Thank for that in-length explanation. If I correctly understand, the reason why I don't have directional arrows everywhere is because of the loops. However, is there a way I can simlate the flux of a commodity inside the network? An edge in a loop will have to carry less water than an the segment in the middle which is unavoidable. How can I model that with ArcGis? Commented Jul 22, 2013 at 12:13