Folks:
I am curious as to how the community is handling survey data as regards utility information (existing water lines, tel Lines, sanitary sewer lines, valves, etc. and additionally storm Inlets, manholes, etc.) in combination with SUDA feature definitions. We currently have a proposed SUDA library with all of our proposed utility/ stormwater/ sanitary sewer information built into it which is working fine on the design end of things, but our survey dumps are strictly survey codes tied to line and cell features. In SS2, we used InRoads Storm and Sanitary to create existing networks from the survey data which was rather cumbersome, but which did provide good results (basically recreating the surveyed utility information within the SDB format).
Are you folks running two SUDA dgnlibs (one for proposed and one for existing utilities data), or are you using a single SUDA library which contains both existing and proposed utilities data? Finally, is there a manner in which to tie the survey codes directly to SUDA feature definitions (i.e., when the survey dump occurs, the codes tie directly to SUDA plan and 3D models and create true existing networks through Survey Processing in situ).
Thanks!
Mark