RE: SUDA and Survey Data

Mark Plum — Mon, 25 Nov 2019 21:24:49 GMT

Thank you so much, Robert. Yours are the ideas which I have had in my own head for a while; yet, with much more detail, of course, LOL.

Kind Regards,

Mark

RE: SUDA and Survey Data

Robert Garrett — Mon, 25 Nov 2019 21:19:57 GMT

Hey Mark:

Starting with the dream: It was once planned by Bentley, hopefully still is, to tie SUDA and Survey feature definitions together such that processing survey also produced a SUDA model. It is not there yet.

But, It is more efficient than the old InRoads workflow (and GEOPAK). Your process will be to use the extract graphics command to produce the SUDA model. Even a oncey-twosey approach is pretty quick. Example: Pick all the waterlines, extract graphics command, voila SUDA waterlines. Keep the survey data in a separate DGN and reference to the SUDA dgn.

Things get super efficient when you use filters. Works on the same principle as Create Terrain Model using filters except you are creating utilities instead of a terrain. The filters segregate things by symbology and/or feature definition allowing you to potentially create an entire SUDA model in one operation. This presupposes that your survey data is consistent and predictable of course.

What libraries do you need? you will have all the following libraries to accommodate this: (I doubt I am telling you anything here you don't already know.)

Survey Feature definitions
Non-Drainage Utilities feature definitions - sometimes my client has asked for exiting to be separate from proposed, but not always. The key distinction is that these are things which do not require a hydraulic model nor hydraulic calculations. water, sewer gas, cables of all sorts.
1. Include the extract graphics filters here IMO
Drainage feature definitions (including sanitary sewer) - it seldom makes sense to separate existing and proposed. And, it is important to including gravity sanitary sewer here because:
1. You can ONLY have one repository for hydraulic prototypes, which is specified by SUDA_Seed_File=. Thus, anything that ever potentially needs to be analyzed hydraulically must be contained in this library:
  1. Sanitary sewer existing and proposed
  2. Drainage existing and proposed.