Of course, this begs the question...why?
Civil Utility group, we must use roadway alignment for profile view (need the stationing, etc.), yet all profile information is regarding proposed utility design, which requires PGL above, and existing pipe crossing at our proposed utility.
export original network...
merge with destination network
reimport
Given existing storm or sanitary pipe network in correct location and elevations... I identify the pipe(s) crossing our proposed utility's alignment, and copy them from their intersection of the proposed utility alignment, perpendicular to the roadway alignment (still part of the source network), and need to move the copied pipe from the source network to another network.
I need them in separate networks, we data reference both... As some of the correctly located pipes and structures get data referenced, and drawn in profile view using our normal styles (i.e., full structure, pipe, etc.) when they're close, or parallel to our proposed utility, whereas pipe crossings are data referenced, and drawn using our crossing style (and must also be moved to roadway alignment in order to display properly).
Unless I have completely overlooked something when creating the data references, while you can override the default parts list, but cannot change an individual pipe's style once data referenced... Hence the need for two networks. CORRECTION: My statement above is correct in that one cannot modify an individual pipe's style via the Properties Palette (which is just dumb)... One _
can_ do so via Toolspace, by expanding the appropriate pipe network's node, pipes, then at the bottom (where I display them), select the desired pipe by name, and _
there_ you can change the individual pipe's style. *sigh*
Thanks for the comments/questions, guys... They helped me work through the issue. Cheers! :beer: