| Product(s): | StormCAD, SewerGEMS, CivilStorm, SewerCAD |
| Version(s): | 08.11.XX.XX and higher |
This article provides troubleshooting tips for various issues that can occur when attempting to import a LandXML file (for example exported from Civil 3D)
When exporting from StormCAD to LandXML, a User Notifcation appears stating one of the following:
"Conduit belongs to a different LandXML pipe ."
"One or more elements contains a blank LandXML network field. LandXML file may not be valid."
"System.ArgumentNullException: Value cannot be null."
"'LandXML Pipe Network' field does not contain data."
When a model is created by importing a LandXML file, a Pipe Network is created as a UDX field. When changes are made to the model and the StormCAD model is exported to LandXML you will notice the errors in question.
To solve the problem, you will need to follow these instructions.
1.) Open the Conduit Flextable.
2.) Click on the Edit button on the top menubar.
3.) Search in the Left Column for LandXML Pipe Network.
4.) Click the Right arrow to Add this field to the Right Column.
5.) Hit OK.
6.) Scroll over to the LandXML Pipe Network Column in the Flextable.
7.) You will notice some elements have "Network - 1" or “PipeNetwork-1” in this field and the rest are blank.
8.) Right Click on the top of the LandXML Pipe Network Column.
9.) Click Global Edit.
10.) Enter the text, "Network - 1" and Hit OK.
11.) Close the Flextable and repeat this process for all of the elements. Typically, this will include the Conduit, Catch Basin, Manhole, Transition, and Outfall elements.
After this is complete, the LandXML file should export correctly.
After importing a LandXML file, you may notice some pipes are missing, and user notifications appear similar to this:
"The conduit Pipe-1 was not imported. The start node is not defined in the LandXML file."
"The conduit Pipe-2 was not imported. The stop node MH-1 is not defined in the LandXML file."
This can be caused by problems with the LandXML file where the connectivity is not properly defined, or did not export correctly from the native application (such as Civil 3D).
First, try importing the XML file back into Civil 3D. If similar errors are seen, you will need to correct the problem on the Civil 3D pipe network side before it can be successfully exported (and imported into the OpenFlows product). Contact Autodesk for help if needed.