|
|
Currently, the InfoDrainage plugin requires the network to be analysed/validated before it can be imported, and this is not currently an option for the foul network and therefore prevents this type of network from being exported.
After speaking to the technical team about this, I was told to convert the foul phase to a surface water before exporting. This is quite a clunky workaround as Civil 3D then picks the network up as a surface water network.
The technical team also noted that this feature is not considered as being urgent but I would argue this is a key feature preventing users from adopting the interoperability between the two software that is currently advertised.
Thank for your taking the time to provide feedback.
I agree with the technical support team that the recommendation would be duplicating the foul phase first so that the original remains unchanged. The duplicated phase can then be converted to a surface water phase and exported to Civil 3D. This ensures the integrity of the original foul design is maintained within InfoDrainage, while still enabling the network to be transferred for coordination in Civil 3D.
We recognise that this is not an ideal or streamlined workflow. However, as we are beginning work on a new interoperability framework, we are not in a position to implement substantial changes to the current integration. Our focus is on delivering a more robust long-term solution rather than incrementally adjusting the existing workflow, as we are well aware of the current limitations and friction points (as it is the case with this one you have raised).