I'm sure this is mentioned somewhere in all the UN documentation and best practices, but when it comes to water lines crossing over each other perpendicularly is the easy solution for having an accurate network to elevate either the whole line or part of the line to make sure it's not the same Z-Value as the one it's crossing?
See screenshot below. If we add a new vertex with higher Z-value to each side of the crossing (shown in red), I assume this will cover our need to have different Z-values.
Here's a vertical profile to illustrate how it would look.
We're not worried about vertically depicting the line perfectly. We don't track Z-Values in our Geometric Network data that will be migrated. Our only concern is making sure there isn't an intersection in the GIS when in real life it crosses over and doesn't actually intersect (i.e. a cross fitting).
Accepted Solutions
@Andy_Morgan - That could work but I believe there is a simpler option if you are talking about it from a connectivity point of view.
The intersecting lines could have the same Z value but not be connected.
If there is no vertex shared by the lines then they aren't "connected"
An example of a switching station in our UN.
The lines intersect with the same z value (0, we don't really model z....yet)
A trace shows that they are not really connected.
@Andy_Morgan - That could work but I believe there is a simpler option if you are talking about it from a connectivity point of view.
The intersecting lines could have the same Z value but not be connected.
If there is no vertex shared by the lines then they aren't "connected"
An example of a switching station in our UN.
The lines intersect with the same z value (0, we don't really model z....yet)
A trace shows that they are not really connected.
