Yes, though it may be slightly tricky. However I'm a bit concerned for your sake about things not being quite the way they should be. Have you already paid someone to set the topology information? If so, and they did it wrongly, maybe it would be best to go back to them? If your client supplied the topology data, well, that may be more difficult (but they should probably at least know). The reason applying topology with this data is the two-dimensional line intersections which are not, in fact, network nodes, because although the lines cross in 2D they are not connected at the crossing point. (The same factor gives rise to the apparent loops, which are not actual loops in the physical network.) This needs special handling. In the normal case it would be easy: you would (if necessary) run Normalize Topology over the network to ensure that all line intersections were at an exactly shared vertex. (You'd actually do this on a copy of the network, since Normalize Topology changes line direction.) Then you'd use the Node Points transform to draw a point at each intersection and at each free line end. Then assign a unique ID to each node point. Then use SQL (probably) to write the FROM_NODE (ID) and TO_NODE (ID) for the start and end of each network line (section, or branch). But that first step could be a problem here, since it would add intersections where lines only appear to cross, without intersecting in the physical network. Node Points would then add points at these non-intersections, so to speak, giving false connectivity. So this network requires special handling. It wouldn't be too hard to find the actual nodes in SQL, at least if we can assume that it is already correctly normalized, so that any intersection where vertices are exactly shared are true network intersections, and not otherwise. (I don't know if that is the case.) I'm happy to try to help with this, but (1) if you've already paid for this to be done, and it hasn't been done properly, then that might be your best approach; and (2) I'd personally only want to help if I could have access to the whole dataset. It might be something you'd prefer to deal with outside the forum. I hope I'm not overcomplicating things. It would be easy to tell you how to shoot yourself in the foot.
|