Whilst setting the coords of a pipe intersection is a good feature, in certain common cases InfoDrainage does not allow for setting the correct setting of grade and levels of pipework, and due to its calculations can output levels against a certain grade that makes the system too slack against the reality that is actually required at said grade. The snip attached demonstrates what I mean, where for example, a large hydrobrake-weir chamber with a sump is located close to a the outlet of an attenuation feature. Due to the short length of interconnecting pipe and large width of the chamber being accounted for in the pipe grade calculation, InfoDrainage will specify levels to a grade that is actually pipe slacker then what is required. The snip attached fully demonstrates this issue, which presents problems when discrepancies are raised between the design layouts / setting out info, and what is in schedules / the model. There should be a feature that enables this to be designed out and keep level in details/drawings the same as the model and correct.
Disclaimer: The development, release, and timing of any features or functionality described or discussed for our products in this User Feedback Forum for Autodesk Water Products and Services remains at our sole discretion. This User Feedback Forum for Autodesk Water Products and Services is not a commitment, promise, or legal obligation to deliver any functionality, is intended solely to outline and gather feedback about our general product direction, and should not be relied on in making purchasing decisions.
Thank you for the suggestion and thanks to those who voted.
I have passed this query to the Customer Success team who will get back to you on the best way to handle pipe intersection coordinates in InfoDrainage, I will also move the status of this suggestion to "Gathering Support" in order to engage in consultations with a wider array of stakeholders to gauge their interest and gather additional perspectives on the proposed feature.
Should we observe a substantial level of enthusiasm and demand, we will be inclined to advance the status of this suggestion to "Under Consideration." This stage will involve a more detailed analysis, including a feasibility study, resource allocation assessment, and preliminary planning to understand how this feature could be seamlessly integrated into the software.