Currently we have generic pipes (ie RCP Class III) and on placement, the user defines the size by using the description field. Because of this, I cannot attach an Item Type and explicitly set the Pay Item information.
If I can set what the size of the conduit should be in the feature definition then I can attach an Item Type and automatically pull in the pay item information by referencing the unique feature definition in the lookup table (ie 18" RCP Class III).
This could be as simple as specifying a default value in the Feature Definition. This would work for me and not break anyone else.
Civil Product Used | OpenRoads Designer |
If you want to create a feature definition that only uses a single pipe size, then you can do so. Create a conduit prototype, and instead of selecting a conduit catalog (which has a series of sizes) select user-defined, and specify the shape and size that you want. Then create a feature definition that uses this prototype. This could result in a large amount of feature definitions though.
An alternative might be to look at how the Item Types are being used - perhaps you could do a look-up that uses the pipe size to find the correct pay item.