LandXML export to hydroflow

[Anonymous]

I am not sure what the issue is, or if it even CAD related, but here goes. On Tuesday I was using the LandXML export to XML pipes in Civil 3D 2008 and importing them into Hydroflow 2005. Today, I do the exact same thing and hydro flow can't process the XML. I tried using an older version of the drawing to export, thinking maybe I did something in CAD to cause the error, but that didn't help. Our company did install a timesheet program and I though maybe this did something,
but a system restore didn't help either. All I know is it worked
Tuesday and now it doesn't. Any ideas...

[annw2]

I haven't used this function yet, but it was a BIG reason for me to pitch the upgrade to my boss. I got sick of having to say that pipe 1 in Hydro was pipe A3 in ACAD. New export was supposed to export labels as well. If this function doesn't work in 3d I will be VERY upset.

[Anonymous]

Sounds like the xml files are different in some way. In order to import an
xml your entire network must be created and/or edited in an upstream to
downstream workflow. If a single pipe was added alternately, downstream to
upstream, then the hydraflow will not import the xml. You can print out the
xml file and verify that all the pipes/structures are listed from upstream
to downstream and determine if there are any incongruities.

Wesley Price

Civil 3D 2007, SP3
Dell Precision PWS390
Intel core 2 CPU 6600 @ 2.4GHz
2 GB of RAM
XP Pro SP3

wrote in message news:5647999@discussion.autodesk.com...
I am not sure what the issue is, or if it even CAD related, but here goes.
On Tuesday I was using the LandXML export to XML pipes in Civil 3D 2008 and
importing them into Hydroflow 2005. Today, I do the exact same thing and
hydro flow can't process the XML. I tried using an older version of the
drawing to export, thinking maybe I did something in CAD to cause the error,
but that didn't help. Our company did install a timesheet program and I
though maybe this did something,
but a system restore didn't help either. All I know is it worked
Tuesday and now it doesn't. Any ideas...

[Anonymous]

Most data associated with the pipe network is exported to hydrastorm since
2007 (if not before). Inverts, rims, names...only need drainage areas
flowing to structures, and longitudal slope before it's nearly fully
automated.

Wesley Price

Civil 3D 2007, SP3
Dell Precision PWS390
Intel core 2 CPU 6600 @ 2.4GHz
2 GB of RAM
XP Pro SP3

wrote in message news:5648970@discussion.autodesk.com...
I haven't used this function yet, but it was a BIG reason for me to pitch
the upgrade to my boss. I got sick of having to say that pipe 1 in Hydro
was pipe A3 in ACAD. New export was supposed to export labels as well. If
this function doesn't work in 3d I will be VERY upset.

[Anonymous]

Had same problem. Another user in our company looked at XML file (double click on the file name in Windows Explorer). He pointed out that for some of the pipes in my system, the XML file said "Flow Direction: NULL". (I had just thrown some pipes & structures into my C3D file, thinking I would do all the editing in HydroFlow.) I found that when I did enough editing of the pipe system in C3d to get the pipes sloping in the correct direction that the "NULL" flow direction changed to + or -. Without the "NULL" flow directions HydroFlow accepted the XML fine and I could carry on.

[annw2]

I've only done the LDD/Civil 2004 out to Hydrstorm. I've never done the import back in. After spending days having to add the labels, I didn't trust the import.

Hydrostorm examines pipes downstream to upstream (headwater analysis) I have also seem it spin networks around into random locations when inserting or reconfiguring systems. Has the import been useful for you? I'm scared to try it at least in 2004.

[Anonymous]

I was working in Civil 3d 2007, and found both import and export worked fine once Hydroflow became convinced I wanted the water flowing downhill instead of up. I am unable to speak to LDD or Civil 3d prior to 2007. Can you make a copy of your project to play around in just to see how it's going to act using import & export? If it works, that becomes your latest & greatest or XML the pipe network from the test project back to the original project or from HydroFlow.

[Anonymous]

I don't import the pipes from hydrastorm either. I've already done that in
civil 3d. I only copy the 100/25 year hgl out to copy into my profiles and
use the reports to support the data provided in the profiles.

wrote in message news:5652112@discussion.autodesk.com...
I've only done the LDD/Civil 2004 out to Hydrstorm. I've never done the
import back in. After spending days having to add the labels, I didn't
trust the import.

Hydrostorm examines pipes downstream to upstream (headwater analysis) I
have also seem it spin networks around into random locations when inserting
or reconfiguring systems. Has the import been useful for you? I'm scared
to try it at least in 2004.

[Anonymous]

Yeah, somebody needs to buy somebody and get it all together, huh? HydraFlow Storm is not nearly as easy to design in as Civil 3d and it can't look at depth other than at the manholes.

[Anonymous]

It seems that there is a giant gap in workflow when going between Hydroflow
Storm Sewers and any cad program. I use all of the default settings for
pipes and inlet structures when possible and that eliminates a lot of data
entry. The problem to me is when revisions begin. I use up a so much time
editing between programs and am always concerned that all the data entry
between programs during revisions will result in some human error. For
example, in our most recent project we have 170 structures and pipes and if
more than 10% changes it seems easier (and more accurate) to re-xml the pipe
network and fill in the blanks again rather that go through and recheck all
of the data by eye.

I'd like to have anyone's opinion on their experiences with Hydraflow
software and any other developers of stormwater design software.

Thanks,

Wesley Price

Civil 3D 2007, SP3
Dell Precision PWS390
Intel core 2 CPU 6600 @ 2.4GHz
2 GB of RAM
XP Pro SP3

wrote in message news:5652487@discussion.autodesk.com...
Yeah, somebody needs to buy somebody and get it all together, huh? HydraFlow
Storm is not nearly as easy to design in as Civil 3d and it can't look at
depth other than at the manholes.

[Civil3DReminders_com]

I haven't used Hydraflow, but I am messing around with the pipe sample VBA code. You could export out the Civil 3D pipe network to Excel and XML in the Hydraflow to Civil 3D in an empty drawing and then export out the Hydraflow model to Excel and compare it in Excel through using sort and if then statements in formulas. This would get rid of the by eye check.

Christopher
http://civil-3d.blogspot.com/

[Anonymous]

Hi Wesley,

The only H/H program I'm familiar with (other than Excel) is StormCAD by
Haestad Methods. You could import LDT pipeworks .mdb file into StormCAD, do
your design, export to a pipework .mdb file and then import that back into
LDT. Worked like a charm. To bad Haestad got bought out by them other
guys.

--
Brian
C3D 2008
http://www.ctcivil.com
http://cadcafe.blogspot.com


"Wesley Price" wrote in message
news:5652655@discussion.autodesk.com...
It seems that there is a giant gap in workflow when going between Hydroflow
Storm Sewers and any cad program. I use all of the default settings for
pipes and inlet structures when possible and that eliminates a lot of data
entry. The problem to me is when revisions begin. I use up a so much time
editing between programs and am always concerned that all the data entry
between programs during revisions will result in some human error. For
example, in our most recent project we have 170 structures and pipes and if
more than 10% changes it seems easier (and more accurate) to re-xml the pipe
network and fill in the blanks again rather that go through and recheck all
of the data by eye.

I'd like to have anyone's opinion on their experiences with Hydraflow
software and any other developers of stormwater design software.

Thanks,

Wesley Price

Civil 3D 2007, SP3
Dell Precision PWS390
Intel core 2 CPU 6600 @ 2.4GHz
2 GB of RAM
XP Pro SP3

wrote in message news:5652487@discussion.autodesk.com...
Yeah, somebody needs to buy somebody and get it all together, huh? HydraFlow
Storm is not nearly as easy to design in as Civil 3d and it can't look at
depth other than at the manholes.

[Anonymous]

That's a good and simple recommendation. Thanks for the suggestion.


wrote in message news:5652971@discussion.autodesk.com...
I haven't used Hydraflow, but I am messing around with the pipe sample VBA
code. You could export out the Civil 3D pipe network to Excel and XML in the
Hydraflow to Civil 3D in an empty drawing and then export out the Hydraflow
model to Excel and compare it in Excel through using sort and if then
statements in formulas. This would get rid of the by eye check.

Christopher
http://civil-3d.blogspot.com/

[Anonymous]

The "null" flow direction on export is a known issue, and it is being
addressed.

Matt

wrote in message news:5651260@discussion.autodesk.com...
Had same problem. Another user in our company looked at XML file (double
click on the file name in Windows Explorer). He pointed out that for some of
the pipes in my system, the XML file said "Flow Direction: NULL". (I had
just thrown some pipes & structures into my C3D file, thinking I would do
all the editing in HydroFlow.) I found that when I did enough editing of the
pipe system in C3d to get the pipes sloping in the correct direction that
the "NULL" flow direction changed to + or -. Without the "NULL" flow
directions HydroFlow accepted the XML fine and I could carry on.

[annw2]

i run into different problems in 2004.

I never have a problem with water flow direction. The uphill comps are standard for headwater calculations as the downstream tail water affects the upstream headwater.

In 2004, the structure & pipe labels don't export. Filling them in in Storm Sewer takes most of the time. I was afraid to try an import as I didn't know if the labels would import & haven't had a chance to try in a scratch project.

I also don't think that the area & curve number & TC export out. I don't remember fields in Pipeworks for that. Don't know about 3d.

I also have problems with reconfiguring lines in Storm Sewer. The lines spin around to random locations. If I imported after that, who knows where the lines would be.

I haven't done an export recently, so don't have example file handy. I also have trouble exporting 2004 Civil/LDD if I have done any graphical edits to the pipe networks. I keep getting error finding nodes & no export. I then have to randomly draw in Storm Sewer. I can't import that back in ACAD.

The chance of fixing any or all of the above was big selling point with boss to upgrade to 3d. Will have to see how it works on next project.