This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Converting back and forth between H20NET (InfoWater) and WaterCAD without using EPANet

We need to convert an H2ONET model into WaterCAD to make some updates. Then convert it back into H2ONET for the client to be able to use in their software. The trouble with using EPANet as the in between is that the pump controls and tank levels etc information is lost in translation. Is there a way to do this and keep all the modeling data in tact?

  • Hello Sydney,

    The EPANET export/import workflow is the best method to exchange data with competitor products. We do not have a direct way to open models between the products, because each product cannot predict the exact file format for each version of the other product. So, we rely on the EPANET standard for data exchange as documented in our Wiki here: Importing or Exporting to WaterCAD, WaterGEMS, HAMMER from other software

    For the EPANET data exchange, the problem is that WaterCAD cannot predict how H2ONET will export its information to EPANET format, and WaterCAD cannot translate unsupported information back to EPANET format. Meaning, there are element types and other information that WaterCAD has but EPANET does not, so assumptions need to be made on export. This is documented in our Wiki here: What are the limitations of importing/exporting EPANET files?

    This may be what is happening on the H2ONET side - it may be making some assumptions or omissions when it exports to EPANET format, in which case there is no way for WaterCAD to keep that information intact if it is not in the EPANET file.

    I would recommend opening the .INP file in EPANET 2 itself, to check if that information you mentioned was lost during the H2ONET export. If you find that the information is present in EPANET but not when importing the file into WaterCAD, try re-saving to .INP format in EPANET itself. This tends to "clean" the file if there are problems with the formatting when the other product exported. This technique is mentioned in this article: Troubleshooting problems with importing EPANET or EPASWMM files

    If the data in question is being lost on the export side (when opening the model back in H2ONET), I would suggest doing the same thing - open the INP file (that WaterCAD exported) in EPANET itself and check if the data is present, then try re-saving to INP format, then open it in H2ONET. 

    If this does not help and the pump and tank information is either being lost when imported into WaterCAD, or when exported from WaterCAD back to EPANET format, please provide a copy of the file for review: Sharing Hydraulic Model Files on the OpenFlows Forum


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

  • Hi Sydney, I received the message you sent us via the "Contact Us" form. I am not sure if you had sent that message before or after I replied to this forum post, so I have sent you a message privately. If you still need assistance, please see the suggestions and requests in my previous reply.


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.