Question regarding "GenericNodeAsset" and POLNode" (OpenRoads Drainage and Utilities)

Hey Mark. But the various references to "Generic" could be best understood as "User Defined".  They are in place in order to allow for utility types which are outside of the mainstream.  When thinking of a list of utility types some things are common and broadly used (water, sewer, gas, etc.).. Those are explicitly defined in the list of utility types in the software.  

But, OpenRoads is intended to account for everything undergrounds, cables, pipes, conduits and ducts of all types.  A statement to this effect still exists in the help and training documents I think.

So, imagine a conduit which is used to ferry hard copy data between two building by way of pneumatic pressure.  True, this could be considered a communications type, but you could also create a generic type of feature definition so it could be reported and presented in a unique way.  You would probably do this specific to a project for such obscure types.

Within feature definitions themselves, the generic and user defined conduit types and network types serve the same purpose, and probably more frequently.  Imagine a hand hole for a comm line.  There is a quite limited list of types of hand hole. So, I would expect that user defined would get used a lot, for folks who care about such things.

POL = Petroleum, Oil, Liquid Gas

Hey Mark. But the various references to "Generic" could be best understood as "User Defined".  They are in place in order to allow for utility types which are outside of the mainstream.  When thinking of a list of utility types some things are common and broadly used (water, sewer, gas, etc.).. Those are explicitly defined in the list of utility types in the software.  

But, OpenRoads is intended to account for everything undergrounds, cables, pipes, conduits and ducts of all types.  A statement to this effect still exists in the help and training documents I think.

So, imagine a conduit which is used to ferry hard copy data between two building by way of pneumatic pressure.  True, this could be considered a communications type, but you could also create a generic type of feature definition so it could be reported and presented in a unique way.  You would probably do this specific to a project for such obscure types.

Within feature definitions themselves, the generic and user defined conduit types and network types serve the same purpose, and probably more frequently.  Imagine a hand hole for a comm line.  There is a quite limited list of types of hand hole. So, I would expect that user defined would get used a lot, for folks who care about such things.

POL = Petroleum, Oil, Liquid Gas

Robert:

   Shortly after posting this question, I decided to apply a few 3D Tops. 3D Bottoms and Plan Cells which I have (primarily traffic signs), create a series of templates, and create some feature definitions for these signs within the GenericNodeAsset category. This idea worked quite well, and I started thinking about all manner of additional objects which could be used within this area... much could be developed as regards general objects- like a sign- which could be placed using the DA/ SUDA tools. While a sign is not exactly a utility- IMO- it does have a footing which could be of use in checking for clashing. 

   I have quite a few objects already within the POLNode area (fuel pumps, oil wells, monitoring wells, etc; surveyed objects), and they were placed there primarily because the structure and network type within the properties seemed to fit them well overall. What I did not understand is what the "L" in POL stood for. You have cleared that up; many thanks!

Best Regards,

Mark

I like the way you think. Our Road Design group is the largest group of CADD Users, so we tend to drive development. Other offices that primarily use CADD for Drafting is our Office of Structures and Office of Traffic and Safety. We are having trouble getting OOS to look at OBD and OBM. The young engineers are excited, but the old dogs aren't interested in new tricks. OOTS is another story. If we could get them to use Open Roads to layout the lighting, signing and signals and have them see how they can draft in 2D and get 3D, quantities and more as a by-product, we hope to win them over.