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

Pipe Geometry

I am looking for pipe geometry in sewercad, I found it in the attribute panel only, previously I used to find it in Flex table under Upstream X (m) and Upstream Y (m); as well for downstream pipe and that was great to copy all to excel, is that feature no longer available and have to go one by one??? or is there other way to get such data? 

Thanks

  • Mohamad,

    Which versions of SewerCAD are you referring to?

    Am I understanding you correctly, you are looking for an upstream node X and Y fields and downstream node X and Y fields in a conduit flex table?

    Thanks,



  • Hi  Akshaya,

    It is 0.8.11.02.75, I do not think there are upstream node X and Y fields and downstream node X and Y fields in a conduit flex table, according to that version. please keep me updated.

    Thanks

  • Hi Mohamad,

    In general, when you open up a conduit table the X and Y field are not available rather Start Node and Stop Node will show. This is what we have in 08.11.02.75 of SewerCAD. 

    When a new version comes out (very soon, in days) you will have an option of creating a two-row flextable. Please create a Conduit table and add, Stop Node, Start Node along with “-X-Upstream Downstream” and “-Y- Upstream Downstream” fields.

     



  • In SewerCAD, StormCAD and SewerGEMS; I am still not able to find the upstream node X and Y fields and downstream node X and Y fields in a conduit flex table, I know there is 2 Row flex table and we can find the info there, but why we are not able to find that in one Row table as before? why when we copy the table to excel we have to modify; in other words "something exist before why eliminated?" is there a way to get the information as before?

    in one row was like that

    Upstream  Upstream  Downstream  Downstream 
    (X) (Y) (X) (Y)



    Regards,
    Mohamad.

  • Mohamad,

    I'm not currently sure why we removed it, but if I had to guess it's probably because after some consideration we found the fields had less value to most people and the information could be found in other places, like the upstream and downstream node properties, even though it might not be quite as convenient. Can I ask what you might need this information for? Maybe there's another solution that we could find to help you.
     
    Regards,
    Mark

    Mark